action #36952
closed
[opensuse][functional][y] test fails in yast2_ftp - ftp configuration takes more time to load than expected
Added by mloviska almost 6 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_ftp
Reproducible¶
Fails since (at least) Build 20180604
Expected result¶
Last good: 20180603 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Due date set to 2018-07-31
- Priority changed from Normal to High
- Target version set to Milestone 18
- Target version changed from Milestone 18 to Milestone 18
- Related to action #37710: [functional][y][fast] test fails in yast2_tftp added
I guess it makes sense to finish #37710 first and then confirm with good statistics if this issue can still appear.
TFTP was failing due to change of workflow in yast, particularly log view was replaced by journal view. It's not clear what is going on with FTP, maybe it is related to bug reported by @dimstar.
- Status changed from New to Blocked
- Assignee set to okurz
Yes, would be worth to track evolution on the bug because the YaST team is currently working on that
- Due date changed from 2018-07-31 to 2018-08-14
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
Seems that again related to the SUT performance. Need to crosscheck with @okurz if we plan to run less worker instances on o3. Issue is not there for SLE.
On top, other problem for performance is that in the test suite we start a lot of services, and do not stop them, so they affect next test suites. Therefore, I would reject this ticket in favor of:
a) having same workers performance as we have for SLE
b) isolating test modules runs (e.g. with feature in os-autoinst to revert to lastgood snapshot even if test was successful if special flag is defined).
Will reject, decide for follow up ticket.
- Status changed from Workable to Resolved
- Assignee set to riafarov
Set TIMEOUT_SCALE=3 to the test suite, as per discussion with okurz.
Have you set a comment on the test suite just as last time referencing a ticket about how to get rid of the timeout scale again?
Also available in: Atom
PDF