-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
1
-
False
-
None
-
False
-
Testable
-
-
I have been performing a release validation test that forces Anaconda into a crash so that this crash could be reported to Bugzilla using Anaconda error reporting functions. However, this process does not work as it crashes for real before the reporting issue is started.
Reproducible: Always
Steps to Reproduce:
1. Download a Fedora image and start Anaconda.
2. While it is running, switch to the Anaconda console.
3. Send "kill -USR1 `cat /var/run/anaconda.pid`"
4. Wait for the crash
Actual Results:
Anaconda crash mechanism crashes with the following message:
Exception in thread AnaExceptionHandlingTest:
Traceback (most recent call last):
File "/usr/lib64/python3.13/site-packages/pyanaconda/core/threads.py", line 288, in run
threading.Thread.run(self)
File "/usr/lib64/python3.13/threading.py", line 992, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib64/python3.13/site-packages/pyanaconda/exception.py", line 400, in raise_exception
eval(compile(code, "str_eval", "exec")) # pylint: disable=eval-used
File "str_eval", line 5, in <module>
File "str_eval", line 3, in 1726142567
RuntimeError: NOTABUG: testing exception handling
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.13/threading.py", line 1041, in _bootstrap_inner
self.run()
File "/usr/lib64/python3.13/site-packages/pyanaconda/core/threads.py", line 285, in run
self._target_failed(sys.exc_info())
File "/usr/lib64/python3.13/site-packages/pyanaconda/core/threads.py", line 267, in _target_failed
sys.excepthook(*exc_info)
File "/usr/lib64/python3.13/site-packages/meh/handler.py", line 168, in <lambda>
self.handleException(DumpInfo(ExceptionInfo(ty, value, tb), obj))
File "/usr/lib64/python3.13/site-packages/pyanaconda/exception.py", line 145, in handleException
exception_lines = traceback.format_exception(*dump_info.exc_info)
File "/usr/lib64/python3.13/traceback.py", line 155, in format_exception
return list(te.format(chain=chain, colorize=colorize))
File "/usr/lib64/python3.13/traceback.py", line 1384, in format
yield from _ctx.emit(exc.stack.format(colorize=colorize))
File "/usr/lib64/python3.13/traceback.py", line 747, in format
formatted_frame = self.format_frame_summary(frame_summary, colorize=colorize)
File "/usr/lib64/python3.13/traceback.py", line 583, in format_frame_summary
show_carets = self._should_show_carets(start_offset, end_offset, all_lines, anchors)
File "/usr/lib64/python3.13/traceback.py", line 701, in _should_show_carets
statement = tree.body[0]
IndexError: list index out of range
Expected Results:
Anaconda crash mechanism should not crash and should be able to report to Bugzilla.
I have found the bug on the textual version of Anaconda where it stops the installation process, however on graphical anaconda, the crash does not stop anaconda from continuing so in the end the system ends up being installed with no problems -> we are talking about a simulated crash however.
I am not sure if Anaconda is not able to catch the simulated crash correctly any more, or if the problem lies in the reporting. The above paragraph however somehow suggests the former.
This seems to be a blocking bug for Fedora release and I will submit it for the Blocker review meeting.
- links to