-
Notifications
You must be signed in to change notification settings - Fork 36
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
rhel-10 and daily-iso tests flakes failing at the end of installation with ERR anaconda:Exception ignored in atexit callback: <function shutdown at 0x7f81dbab1e40>"" #1296
Comments
Packages diff: |
Last week occurence: 30 / 7 dailies which is 1/50 test runs. |
This is weird, it looks like the Anaconda is turning off the logging log gets released and somehow it changes into SIGTERM signal processing... |
I just saw this in the python documentation:
https://docs.python.org/3/library/logging.html#thread-safety I wonder if this is not the issue we are hitting. |
Since 10-11-2024 appearing also on daily-iso |
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.
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.
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.
First spotted 08-29-2024.
08-28-2024 does not have logs for a different issue.
08-27-2024 did not hit the problem.
Hit ~ 6/1000 test runs in the last week's dailies.
kstest.log
virt-install.log
virt-install.log
virt-install.log
virt-install.log
virt-install.log
virt-install.log
The text was updated successfully, but these errors were encountered: