action #47246
closed
[opensuse][functional][y] Get rid of TIMEOUT_SCALE in kde testsuite on o3 if still there or adjust test suite
Added by okurz almost 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 23
- Copied from action #37000: [opensuse][functional][u][sporadic] test fails in reboot_plasma5 - either stuck in shutdown or not enough waiting time for grub2? added
- Assignee deleted (
oorlov)
Oliver, it seems like you copied a ticket that was assigned to me and did not remove assignee. I removed it.
- Due date deleted (
2019-02-26)
I don't see any priority in this, so putting to the product backlog. Discussed it with @oorlov, it's not 5 minutes task as we need to adjust all timeouts that were increased by the setting for no gain. Removing the setting will bring test suite back to unstable results, as in #37000.
Well, if you say so. For which sprint do you suggest to schedule then? I think for tickets within the same milestone period that we already are in it is less moving tickets around when we just suggest a later sprint or directly schedule for a later milestone, OK?
- Due date set to 2019-03-26
- Status changed from New to Rejected
- Assignee set to riafarov
@okurz, seems that you don't understand the point. I reject the ticket, in case you feel like TIMEOUT_SCALE should be removed from that particular test suite I vote for disabling whole test suite. It's unstable and we can spend months to make it stable to spare some execution time. Team doesn't feel like it, sorry. If you want to push for it, I need opinions of stakeholders and not PO who uses her/his position to force people follow personal wishes. Yellow card for this one ;)
TIMEOUT_SCALE just for shutdown seems over the top. If the shutdown test ist problematic on KDE specifically, can we add the extra waits with a soft fail there please?
Also, do we have a bug number where we could potentially involve a developer with actually fixing KDE?
Also available in: Atom
PDF