Skip to content
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

Include more logging related to test execution (test start, test end, timestamps) #3287

Open
rasibley opened this issue Oct 14, 2024 · 1 comment
Assignees
Milestone

Comments

@rasibley
Copy link
Contributor

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:

[   85.586564] restraintd[4212]: ** Fetching task: 184687307 [/mnt/tests/distribution/install/tag-repository] 
[   88.398025] restraintd[4212]: ** Preparing metadata 
[   89.399494] restraintd[4212]: ** Refreshing peer role hostnames: Retries 0 
[   90.380893] restraintd[4212]: ** Updating env vars 
[   90.381091] restraintd[4212]: ** Updating external watchdog: 2400 seconds 
[   91.370516] restraintd[4212]: ** Installing dependencies 
[  110.108446] restraintd[4212]: ** Running task: 184687307 [/distribution/install/tag-repository] 
[  112.548781] restraintd[4212]: ** Completed Task : 184687307 

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.

@juk
Copy link
Collaborator

juk commented Oct 15, 2024

Similar issue #1409

@happz happz self-assigned this Nov 21, 2024
@happz happz added this to the 1.40 milestone Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants