Project

General

Profile

Actions
Copy link

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 about 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
Due date:
2019-03-26
% Done:

0%

Estimated time:
Difficulty:

Description

I saw in https://openqa.opensuse.org/tests/848407 (latest) that the test suite description references #37000 with TIMEOUT_SCALE. No test suite should have TIMEOUT_SCALE set forever but only as temporary mitigation.

Related issues 1 (0 open — 1 closed)

Copied from openQA Tests - action #37000: [opensuse][functional][u][sporadic] test fails in reboot_plasma5 - either stuck in shutdown or not enough waiting time for grub2?Resolvedoorlov2018-06-082018-09-25

Actions
Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • 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
Actions
Copy link
 #2

Updated by oorlov about 5 years ago

  • Assignee deleted (oorlov)

Oliver, it seems like you copied a ticket that was assigned to me and did not remove assignee. I removed it.

Actions
Copy link
 #3

Updated by riafarov about 5 years ago

  • 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.

Actions
Copy link
 #4

Updated by okurz about 5 years ago

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?

Actions
Copy link
 #5

Updated by okurz about 5 years ago

  • Due date set to 2019-03-26
Actions
Copy link
 #6

Updated by riafarov about 5 years ago

  • 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 ;)

Actions
Copy link
 #7

Updated by lnussel about 5 years ago

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?

Actions
Copy link

Also available in: Atom PDF