You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Beaker/Restraint, we can see clearly in the console.log when a test began and ended, this is critical for for kernel debugging (Automotive and RHEL) to identify which test may have caused a kernel panic/oops. Example snippet of how this looks in Restraint when viewing the console.log:
It would be nice if we had a similar capability in tmt/Testing Farm so that more details related to test execution is logged in dmesg which would then be propogated in the console log as well.
The text was updated successfully, but these errors were encountered:
For Beaker/Restraint, we can see clearly in the console.log when a test began and ended, this is critical for for kernel debugging (Automotive and RHEL) to identify which test may have caused a kernel panic/oops. Example snippet of how this looks in Restraint when viewing the console.log:
It would be nice if we had a similar capability in tmt/Testing Farm so that more details related to test execution is logged in dmesg which would then be propogated in the console log as well.
The text was updated successfully, but these errors were encountered: