action #16022
closed
test fails in command_not_found Build0209
Added by dgutu over 7 years ago.
Updated over 7 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-ppc64le-sles+extratests_ppc@ppc64le fails in
command_not_found
Reproducible¶
Fails since (at least) Build 0187
Expected result¶
If the package is not installed then we should get the out like 'cnf $pkg_to_install'
Further details¶
Always latest result in this scenario: latest
@asmorodskyi Is there a special reason for using this option?
This breaks common expectations that test developers have about bash scripts.
@dheidler "common expectations" is too tricky term to use it as reason for changing the code. Please provide more clear reasons why it was better when we ignore errors . From my side I can say that the reason to enable pipefail was because I found several places where bash scripts was actually failing and do nothing but we were green because pipefail was disabled. In other words with that PR I was trying to lower down chance of "false positives" in tests.
Well - It's ok - I can update my test.
It's just a bit odd when something, that I tried on my local machine
doesn't work in openQA because of this flag being set.
- Status changed from New to In Progress
- % Done changed from 0 to 100
merged, please reference a production system job showing the correct behaviour
as soon as finished and resolve the ticket
- Status changed from In Progress to Resolved
Also available in: Atom
PDF