-
Notifications
You must be signed in to change notification settings - Fork 355
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
Suppress tracebacks when SIGTERM signal processing #5939
Suppress tracebacks when SIGTERM signal processing #5939
Conversation
/kickstart-test --skip-testtypes whatever |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me as a hotfix. :)
Seems we are still seeing the same issue (in 2 tests from the run)?
|
OK, at least we know this is not the solution. |
60578f9
to
9c6c635
Compare
Let's use this PR for testing purpose. |
/kickstart-test --skip-testtypes whatever |
No fails with the logging traceback here. Running the batch again. |
/kickstart-test --skip-testtypes whatever |
So we have a confirmation that the issue is not running threads in the background. In that case let's try something different. |
This is a workaround for rhinstaller/kickstart-tests#1296 where we are most likely hitting issue that logging is not safe to use in the signal handlers because logging is not reentrant safe. To avoid failures in KS tests and also test if this is the correct issue, let's use this workaround. The ideal fix should be to not use logging in atexit call which might be tricky to resolve and also we will use a lot of log outputs.
9c6c635
to
7d6c119
Compare
/kickstart-test --skip-testtypes whatever |
Let's try to prevent logging to raise exceptions. |
We have a full exception first time:
In any case it looks that the exception is not that helpful because it's just interrupted stack. The main issue is that even
which is the new code in the Wayland solution which is causing all stderr prints to go to journal. However, that doesn't solve mystery of why it is even printed and what is causing that... |
7d6c119
to
2ca7f3c
Compare
/kickstart-test --skip-testtypes whatever |
One of the possible solutions could be to remove |
/kickstart-test --skip-testtypes whatever |
1 similar comment
/kickstart-test --skip-testtypes whatever |
Should be properly resolved by #5962 |
This is a workaround for
rhinstaller/kickstart-tests#1296
where we are most likely hitting issue that logging is not safe to use in the signal handlers because logging is not reentrant safe. To avoid failures in KS tests and also test if this is the correct issue, let's use this workaround.
The ideal fix should be to not use logging in atexit call which might be tricky to resolve and also we will use a lot of log outputs.