action #42122
closed
coordination #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
Added by riafarov over 5 years ago.
Updated over 5 years ago.
Target version:
SUSE QA - Milestone 21
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
- 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
- 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.
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.
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.
- 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.
- Status changed from Workable to In Progress
- Assignee set to oorlov
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- 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
Also available in: Atom
PDF