Project

General

Profile

Actions

action #16022

closed

test fails in command_not_found Build0209

Added by dgutu over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-01-16
Due date:
% Done:

100%

Estimated time:
Difficulty:

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

Actions #2

Updated by dheidler over 7 years ago

@asmorodskyi Is there a special reason for using this option?
This breaks common expectations that test developers have about bash scripts.

Actions #3

Updated by asmorodskyi over 7 years ago

@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.

Actions #4

Updated by dheidler over 7 years ago

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.

Actions #5

Updated by dheidler over 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 100
Actions #6

Updated by okurz@suse.de over 7 years ago

merged, please reference a production system job showing the correct behaviour
as soon as finished and resolve the ticket

Actions

Also available in: Atom PDF