[qe-core][functional] Ensure temporary TIMEOUT_SCALE values can be removed again in standard scenarios, e.g. "kde"
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.
#2 Updated by riafarov about 2 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.
#4 Updated by okurz about 1 year 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).