Project

General

Profile

action #71602

[qe-core][functional][osd] default "gnome" test suite on osd has no video due to max_job_time above default which is only necessary in some cases

Added by okurz about 1 year ago. Updated 5 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

<fcrozat> are video still recorded for staging tests ? I can't find the link in https://openqa.suse.de/tests/4710118#downloads
<okurz> https://openqa.suse.de/tests/4710118/file/worker-log.txt shows that there was NOVIDEO=1 so no video recorded
<dzedro> Frédéric Crozat there have been change, you have to set NOVIDEO=0 to have video
<okurz> that should not be necessary by default, only if MAX_JOB_TIME exceeds the default of 2h
<okurz> so someone set a MAX_JOB_TIME>2h on the generic "gnome" test suite which then in turn disables the video by default. I recommend to delete the MAX_JOB_TIME again. Normally there should really be no need to exceed 2h
<dzedro> I guess it's bcause of aarch64 https://openqa.suse.de/tests/4702106 or some oher arch, as aarch64 has MAX_JOB_TIME=10800
<okurz> hm, if it's two times slower on aarch64 should not mean we need to have the higher timeout on the test suite. I guess setting MAX_JOB_TIME=10800 on the aarch64 machines is a better approach. I found out in the audit database that it was Dominik Heidler changing that 2019-12-02 . Dominik Heidler WDYT could you set the MAX_JOB_TIME on the slow machines rather than test suites?


## Tasks

- Remove test modules from **gnome** that are not directly related to gnome, like mysql, sssd, etc.

Related issues

Related to openQA Tests - coordination #68794: [qe-core][functional][epic] rework postfail hooksNew2020-03-31

Related to openQA Tests - action #71716: No video uploaded when `aarch64_cpu_max` is usedRejected2020-09-23

Blocked by openQA Tests - action #76870: O3: Replace extra_tests_on_gnome with YAML scheduled extra_tests_gnomeResolved2020-11-02

History

#1 Updated by dheidler about 1 year ago

Wouldn't that disable video completely by default on aarch64?

#2 Updated by dheidler about 1 year ago

I guess it could make more sense to set NOVIDEO=0 in the gnome testsuite.

#3 Updated by dheidler about 1 year ago

  • Assignee changed from dheidler to SLindoMansilla

for grooming

#4 Updated by okurz about 1 year ago

Probably the best solution would be to ensure that the default "gnome" testsuite is well below 2h even with post_fail_hooks running by moving test modules to specific extra tests. Then no MAX_JOB_TIME is needed at all and no problem with the video exclusion happens.

#5 Updated by szarate about 1 year ago

#6 Updated by ggardet_arm 12 months ago

  • Related to action #71716: No video uploaded when `aarch64_cpu_max` is used added

#7 Updated by SLindoMansilla 12 months ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee deleted (SLindoMansilla)
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h

#8 Updated by dheidler 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler

#9 Updated by dheidler 11 months ago

  • Status changed from In Progress to Blocked

Blocked by #76870 - deprecated non-YAML scheduled extra_tests_on_… testsuites should not be touched anymore.

#10 Updated by dheidler 11 months ago

  • Blocked by action #76870: O3: Replace extra_tests_on_gnome with YAML scheduled extra_tests_gnome added

#11 Updated by tjyrinki_suse 11 months ago

  • Subject changed from [functional][u][osd] default "gnome" test suite on osd has no video due to max_job_time above default which is only necessary in some cases to [qe-core][functional][osd] default "gnome" test suite on osd has no video due to max_job_time above default which is only necessary in some cases

#12 Updated by dheidler 10 months ago

  • Status changed from Blocked to In Progress

The gnome testsuite seems to have already about the same runtime as the extra_tests_gnome one.
So we would only shift the problem by moving test modules.
Therefore I will go with the NOVIDEO=0 approach.

#13 Updated by dheidler 10 months ago

  • Status changed from In Progress to Feedback

#14 Updated by okurz 10 months ago

dheidler wrote:

The gnome testsuite seems to have already about the same runtime as the extra_tests_gnome one.
So we would only shift the problem by moving test modules.
Therefore I will go with the NOVIDEO=0 approach.

That does not make sense to me. The extra_tests scenarios have the benefit of being more independant. And gnome is one of the scenarios also used in staging. This is what this ticket is about. Can you please see the specific suggestion "Remove test modules from gnome that are not directly related to gnome, like mysql, sssd, etc."? Of course they don't need to go into extra_tests_gnome, they could also go into something like extra_tests_services or so.

#15 Updated by dheidler 10 months ago

But wouldn't that mean that we would loose test coverage in staging?

#16 Updated by okurz 10 months ago

dheidler wrote:

But wouldn't that mean that we would loose test coverage in staging?

true. This means that staging tests likely want a setup for "extra tests" as well or handle it differently in the scenarios for staging and non-staging

#17 Updated by dheidler 6 months ago

  • Status changed from Feedback to Workable
  • Assignee deleted (dheidler)

#18 Updated by tjyrinki_suse 5 months ago

  • Priority changed from High to Normal
  • Target version deleted (Milestone 30)
  • Start date deleted (2020-09-21)

Also available in: Atom PDF