[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
<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.
#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.
#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
gnometestsuite seems to have already about the same runtime as the
So we would only shift the problem by moving test modules.
Therefore I will go with the
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.