action #89260
closed
[leap 15.3] test fails in mutt - mutt command not found
Added by lkocman about 3 years ago.
Updated about 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
Seems like mutt didn't get installed during this test.
openQA test in scenario opensuse-15.3-DVD-ppc64le-extra_tests_in_textmode@ppc64le fails in
mutt
Test suite description¶
Maintainer: okurz@suse.de
Mainly console extratest.
Reproducible¶
Fails since (at least) Build 32.4
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Interestingly also bash mdadm.sh failed.
- Subject changed from test fails in mutt - mutt command not found to [leap 15.3] test fails in mutt - mutt command not found
- Assignee set to jbaier_cz
@jbaier_cz as you are the maintainer of the test module "mutt" I suggest you take a look into this. I can see the line
zypper_call("in mutt", exitcode => [0, 102, 103]) if (is_tumbleweed || is_jeos || get_var('PUBLIC_CLOUD'));
Why not just ensure that it is always installed regardless of the product? The test module summary does not tell that, could be that there is a good reason why mutt should be expected to be already present as pre-installed.
Sure, I will look at this. The original intention was probably to fail if mutt is not present on SLES by default. It might be also a coincidence as I did not find any documentation suggesting this. I will fix that by the end of the week.
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF