action #16446
closed
[sle][functional]test fails in yast2_i because unexpected char was typed
Added by asmorodskyi about 7 years ago.
Updated over 6 years ago.
Category:
Feature requests
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-aarch64-textmode@aarch64 fails in
yast2_i
Instead of "nfs-client" you can see "nfs-clienmt"
Looks like issue could be related to #poo12250 but difference that in this case there is no "queue is full" errors in the log
Reproducible¶
Fails since (at least) Build 0232 (current job)
Expected result¶
Last good: 0231 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Project changed from openQA Tests to openQA Project
- Category changed from Bugs in existing tests to 132
- Subject changed from test fails in yast2_i because unexpected char was typed to [sle][functional]test fails in yast2_i because unexpected char was typed
- Target version set to Milestone 11
Unfortunately the failing tests are not available anymore. However, the latest job in this scenario didn't fail. So this seems to occur either only sometimes or has already been fixed.
- Status changed from New to Rejected
As fairly mentioned by @mkittler, issue description is outdated, we don't see this problem on SLE15 atm, hence reject. In case issue appears, I suggest to create a new ticket with proper description.
Also available in: Atom
PDF