action #38138
closed
[qam] [sle15] test fails in userspace_coreutils - qa_test_coreutils not properly updated for sle15
Added by pcervinka almost 6 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Server-DVD-Updates-x86_64-mau-qa_userspace_coreutils@64bit fails in
1_coreutils
Reproducible¶
Fails since (at least) Build 20180622-2
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-qa_userspace_coreutils
https://openqa.suse.de/tests/1835465
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-qa_userspace_coreutils
https://openqa.suse.de/tests/1884484
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-qa_userspace_coreutils
https://openqa.suse.de/tests/1951018
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: mau-qa_userspace_coreutils
https://openqa.suse.de/tests/2019480
Is anyone working on the qam backlog?
Guys, userspace now maybe maintained by QAF team. I'm willing to help but really busy on fixing kernel tests issue :(
Oliver could you please check/confirm statement "userspace now maybe maintained by QAF team"? Thank you. Unfortunately QAM has no resources to fix tests in qa-testsuites at the moment.
General note: If we won't find somebody to fix them, we will probably exclude failing tests from SLE15 job groups.
- Status changed from New to In Progress
- Assignee set to yosun
userspace_coreutils was removed from Maintenance: SLE 15 GA Updates till it is sorted out.
@okurz, Sorry for the late reply, just notice it. BTW, I'll remember the name QSF correctly :)
@pcervinka
The hint is to look into why it fails, coreutils test commands in userspace, different product version has different coreutils version and the command's input/output may different. Try to manually type those commands and check the output, if it's not a product bug, then change the test code by patch. e.g. qa-testsuites/tests/qa_test_coreutils/sle15.patch
Inside of this example patch, there is a fix about "mv-special-1", and you can see this sub testcase run passed in the "failed tests".
- Status changed from In Progress to Resolved
Also available in: Atom
PDF