Actions
action #71602
open[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
Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
2022-02-18
Due date:
% Done:
100%
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?
Acceptance criteria¶
- AC1: Default test suites, at least "gnome", does not need an explicit MAX_JOB_TIME specified anymore on the test suite
- AC2: MAX_JOB_TIME is only specified where needed
- AC3: Staging tests coverage is unchanged, e.g. the same test modules are still scheduled as part of staging tests independant of the actual scenario
Tasks¶
- Move test modules from gnome that are not directly related to gnome, like mysql, sssd, etc. to an according "extra_tests" test suite
Actions