run_ltp: Print tasktrace on test failure #18909
Conversation
mdoucha
force-pushed
the
ltp_tasktrace
branch
2 times, most recently
from
7e020a7 to
7d92678
Compare
There was a problem hiding this comment.
LGTM, thanks for this!
I was looking for something else which would be useful to dump (https://docs.kernel.org/admin-guide/sysrq.html), but it looks only t and w. Or maybe l (Shows a stack backtrace for all active CPUs.)?
BTW many of these do on my laptop: this sysrq option is disabled.
Yes, SysRq features can be disabled via But I guess I'll have to take a look at PPC support later, crashdump and tasktrace don't work as expected there: |
The run_ltp debug features need active VNC console to run some optional commands. However, logging in after test failure may not be possible due to the system being frozen. Preinitialize VNC console after boot so that at least SysRq shortcuts can be used to generate crashdump.
Add support for optionally printing process backtraces and blocked tasks on test failure.
If the command to terminate tcpdump times out, restore the previous console. Otherwise OpenQA may get confused which console should be active after VM snapshot reload.
|
I've increased tasktrace |
Add support for optionally printing process backtraces and blocked tasks on test failure.
Also add minor fixes for corner cases in tcpdump and crashdump handling.