action #42122
closedcoordination #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x
[functional][y][fast] adjust yast2_nis test module to be executed on s390x
0%
Description
Observation¶
There is a warning which we didn't expect, need to validate it if it's expected and adjust test code.
Another possibility can be that entry we add is not removed and we proceed with execution.
NOTE: In case many differences are identified, simply remove it from schedule for s390x architecture with a comment.
openQA test in scenario sle-12-SP4-Server-DVD-s390x-yast2_ncurses@s390x-kvm-sle12 fails in
yast2_nis
Reproducible¶
Fails since (at least) Build 0396
Expected result¶
Last good: https://openqa.suse.de/tests/2130795#step/yast2_nis/14
Further details¶
Always latest result in this scenario: latest
Updated by riafarov over 5 years ago
- Subject changed from [functional][y] adjust yast2_nis tets module to be executed on s390x to [functional][y] adjust yast2_nis test module to be executed on s390x
Updated by okurz over 5 years ago
- Target version set to Milestone 21
How about we just skip this module from execution on s390x? I doubt that we will gain a lot of value for this module to be used on s390x as well.
Updated by riafarov over 5 years ago
I guess it should have been clarified before we even started work on adjusting tests for s390x. Does any of them have value on s390x? On top, that's unclear if that warning makes sense or it's a bug. But still, I would evaluate efforts to fix test, as it should work without any major changes.
Updated by okurz over 5 years ago
riafarov wrote:
[…] Does any of them have value on s390x?
Yes, all have value but we need to look at "value per effort" to make a decision where our limited capacity is best invested in.
Updated by riafarov over 5 years ago
- Description updated (diff)
okurz wrote:
riafarov wrote:
[…] Does any of them have value on s390x?
Yes, all have value but we need to look at "value per effort" to make a decision where our limited capacity is best invested in.
Absolutely, but my point is that we don't know what is the effort + it's potential bug. If it's too complex, we simply exclude it. I've added more explicit comment there.
Updated by oorlov over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by oorlov over 5 years ago
- Status changed from In Progress to Feedback
The issue happened, because NIS Domain field is prefilled with 'suse.de' on s380x installation, and the test just adds 'suse.de' again to the same string. Please see the screenshot from the step as an example ("suse.desuse.de" is typed in NIS Domain field).
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5976
Needles PR: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/965
Updated by oorlov over 5 years ago
- Status changed from Feedback to Resolved
The module run passed on osd: https://openqa.suse.de/tests/2183103
Updated by oorlov over 5 years ago
- Subject changed from [functional][y] adjust yast2_nis test module to be executed on s390x to [functional][y][fast] adjust yast2_nis test module to be executed on s390x
- Due date changed from 2018-11-06 to 2018-10-23
Updated by oorlov over 5 years ago
The module failed once on SLE15, because font there differs from the SLE12. I've added the appropriate needle for SLE15 and it also passed: https://openqa.suse.de/tests/2188577#step/yast2_nis/19