-
Notifications
You must be signed in to change notification settings - Fork 115
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
better logging of fam failures #16967
Conversation
|
PRT Result
|
ad2bd00
to
67efb89
Compare
|
PRT Result
|
|
PRT Result
|
|
PRT Result
|
|
PRT Result
|
4221c48
to
7c562af
Compare
|
PRT Result
|
tests/foreman/sys/test_fam.py
Outdated
module_target_sat.get('/tmp/pytest.stdout', 'pytest.stdout') | ||
module_target_sat.get('/tmp/pytest.stderr', 'pytest.stderr') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can't be the right approach :(
7c562af
to
8059901
Compare
|
PRT Result
|
|
PRT Result
|
8059901
to
9d792a5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't be easier :)
trigger: test-robottelo |
trigger: test-robottelo |
PRT Result
|
PRT Result
|
(cherry picked from commit 04976cc)
better logging of fam failures (#16967) (cherry picked from commit 04976cc) Co-authored-by: Evgeni Golov <[email protected]>
Problem Statement
The output of FAM tests is mangled due to how pytest tries to print the big
result
object.There are no linebreaks and it's super hard to find the failure.
Additionally the double assert is pointless, as it asserts twice the same thing: the result is successful.
Solution
Stop asserting
PASSED
in stdout (additionally saves the case where there is the stringPASSED
in the output for some reason, but the test actually failed).Pass a custom error output to the
status == 0
assertion, including stdout, stderr and the status code.Related Issues