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.

Sign up for GitHub

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

Jump to bottom

locked mock failure not reported to jtreg logs #3

Closed
andrlos opened this issue Mar 31, 2021 · 1 comment
Closed

locked mock failure not reported to jtreg logs #3

andrlos opened this issue Mar 31, 2021 · 1 comment

Comments

@andrlos
Copy link
Collaborator

andrlos commented Mar 31, 2021 •
edited
Loading

the jtreg logs dont seem to be logging the failure with locked chroot (mock), this results in seemingly passing tests whereas in reality the test didnt even properly run due to the failure

How to reproduce:
chroot should get locked for any old fedora version in init arguments in utils/mock/mock_executor.py, starting old fedoras start at "f31" currently

results:
see jtregLogs logs of binaries test or any other testscase, that reports locked chroot into jsf.log and see, that there is no mention about the locked chroot in jtregLogs whatsoever

expected results:
failure about locked chroot recorded in jtregLogs in the relevant file (e.g. BinariesTest_*.jtr.xml for binaries test)
@andrlos andrlos mentioned this issue Apr 10, 2021
Merged
andrlos added a commit that referenced this issue Apr 11, 2021
@andrlos
Merge pull request #5 from NikolSkvarilova/master
2223a1e 
Fixed reporting locked mock failure to jtreg logs (Issue #3)
@andrlos
Copy link
Collaborator Author

andrlos commented Apr 11, 2021

e16efc9

@andrlos andrlos closed this as completed Apr 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andrlos