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

check dmesg overwrites itself with tests that reboot #3317

Open
sbertramrh opened this issue Oct 24, 2024 · 0 comments
Open

check dmesg overwrites itself with tests that reboot #3317

sbertramrh opened this issue Oct 24, 2024 · 0 comments
Assignees
Labels
area | check Test check implementation
Milestone

Comments

@sbertramrh
Copy link

tmt-reboots dmesg-after will run when the reboot is called. Not an issue in general but the problem occurs when the test completes or has multiple reboots, the name of the file used to save it is the same.
/var/tmp/tmt/run-022/kernel-automotive/plans/sst_kernel_ft/memory/plan/execute/data/guest/default-0/external_er/memory/config_memtest/config_memtest-1/checks/dmesg-after-test.txt
So it will be overwritten each time and only the very last one will remain. I think the same is happening with the dmesg-before-test.txt as well. Can we index this during a single test run so that we have the contents of all the captures?

Can we create the log file capture from dmesg with the epoch date appended in the name, so something like:
dmesg-after-test-$(date +%s).txt?
Or equivalent for python syntax.

@happz happz added the area | check Test check implementation label Oct 24, 2024
@happz happz self-assigned this Oct 24, 2024
@happz happz added this to the 1.39 milestone Oct 24, 2024
@martinhoyer martinhoyer modified the milestones: 1.39, 1.40 Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area | check Test check implementation
Projects
None yet
Development

No branches or pull requests

3 participants