[qam] [sle15] test fails in userspace_coreutils - qa_test_coreutils not properly updated for sle15
#8 Updated by pcervinka about 3 years ago
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.
#9 Updated by okurz about 3 years ago
- Status changed from New to In Progress
- Assignee set to yosun
Yes, it is true that QSF (not QAF) has the official responsibility for the "userspace regression" test suites but we can only attend them with very limited ressources and rather long reaction times.
Nevertheless, we have the equivalent scope of tests running for the current development builds in the SLE15 codestream, i.e. currently SLE15-SP1 and the tests are passed there (mainly), e.g. see
https://openqa.suse.de/tests/latest?test=qa_userspace_coreutils&arch=x86_64&version=15-SP1&machine=64bit&flavor=Installer-DVD&distri=sle showing e.g. https://openqa.suse.de/tests/2072810 which is the last job that successfully executed. I recommend to compare differences between these tests and the QAM ones. What I do not understand is the difference in the test schedule. https://openqa.suse.de/tests/2073453 is the latest failing "qam" test that schedules the module "userspace_coreutils" whereas the 15SP1 one schedules "execute_test_run".
yosun, can you understand the difference and provide hints there?
#11 Updated by yosun almost 3 years ago
- Assignee deleted (
okurz, Sorry for the late reply, just notice it. BTW, I'll remember the name QSF correctly :)
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".