-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration test for stopping target service of proxy feature broken #772
Comments
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Mar 4, 2024
Relates to: eclipse-bluechi#772 When pytest-timeout triggers a timeout is triggered, the test will be exited with pytest.fail and test artifacts might not be collected - so debugging issues with timeouts become hard to debug. Therefore, replace pytest-timeout with a slim, custom implementation that throws an error when timeout is reached. In addition, lets distinguish between timeouts for setup, test execution and artifact collection. Signed-off-by: Michael Engel <mengel@redhat.com>
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Mar 4, 2024
Relates to: eclipse-bluechi#772 When pytest-timeout triggers a timeout is triggered, the test will be exited with pytest.fail and test artifacts might not be collected - so debugging issues with timeouts become hard to debug. Therefore, replace pytest-timeout with a slim, custom implementation that throws an error when timeout is reached. In addition, lets distinguish between timeouts for setup, test execution and artifact collection. Signed-off-by: Michael Engel <mengel@redhat.com>
It seems there are logs about too many open files:
So this might be related to podman and the GH hosts in the CI. Update: |
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Mar 4, 2024
Relates to: eclipse-bluechi#772 When pytest-timeout triggers a timeout is triggered, the test will be exited with pytest.fail and test artifacts might not be collected - so debugging issues with timeouts become hard to debug. Therefore, replace pytest-timeout with a slim, custom implementation that throws an error when timeout is reached. In addition, lets distinguish between timeouts for setup, test execution and artifact collection. Signed-off-by: Michael Engel <mengel@redhat.com>
engelmi
added a commit
that referenced
this issue
Mar 4, 2024
Relates to: #772 When pytest-timeout triggers a timeout is triggered, the test will be exited with pytest.fail and test artifacts might not be collected - so debugging issues with timeouts become hard to debug. Therefore, replace pytest-timeout with a slim, custom implementation that throws an error when timeout is reached. In addition, lets distinguish between timeouts for setup, test execution and artifact collection. Signed-off-by: Michael Engel <mengel@redhat.com>
Should be fixed by #820 feel free to reopen if appears again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It seems that the
proxy-service-stop-service
feature is broken in the GH CI:https://github.com/eclipse-bluechi/bluechi/actions/runs/8138365284/job/22240289714?pr=770#step:8:175
Running tests locally in the contianer setup doesn't lead to a failure.
It receives a timeout while waiting for the
requesting.service
to start (which resolves the proxy dependency).Note:
Its currently a bit hard to debug since no journal logs and other artifacts are collected due to the pytest timeout (which can't be caught and its not intended to do so, apparently). Therefore, a small and simple custom implementation of a signal-based timeout might be better in the future.
To Reproduce
Running integration tests in the CI
Expected behavior
Test passes
The text was updated successfully, but these errors were encountered: