Project

General

Profile

Actions

action #63388

open

[qe-core][functional] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde"

Added by okurz almost 5 years ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
Start date:
2020-02-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

As I realized myself I can answer my question in #3700#note-28 : We do set "TIMEOUT_SCALE=3" in tests, e.g. as visible in https://openqa.opensuse.org/tests/1171538# which also the test suite description reflects. TIMEOUT_SCALE is meant as a temporary measure or for really slow workers which we should not have at all in production. Where necessary we should bump internal timeouts, then remove TIMEOUT_SCALE and also adjust the testsuite settings please.

Actions #1

Updated by riafarov almost 5 years ago

  • Target version set to future
Actions #2

Updated by riafarov about 4 years ago

  • Subject changed from [functional][y][u] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde" to [functional][u] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde"

I would opt to reject as we need better solution than hoping that with lower timeouts tests will work stably.

Actions #3

Updated by tjyrinki_suse about 4 years ago

  • Subject changed from [functional][u] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde" to [qe-core][functional] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde"
Actions #4

Updated by okurz about 3 years ago

I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives

First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions #5

Updated by slo-gin about 2 years ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #6

Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF