action #169549
closedSTART_AFTER_TEST seems doesn't work for some certain test suites size:s
0%
Description
START_AFTER_TEST seems doesn't work for some certain test suites (I mean X11 related test suites under the job group "Desktop Applications" https://openqa.suse.de/tests/overview?result=incomplete&arch=&flavor=&machine=&test=&modules=&module_re=&group_glob=¬_group_glob=&comment=&distri=sle&version=15-SP7&build=38.1&groupid=118#)
I didn't see this issue for Wayland related test suites.
Let's take x11-desktopapps-firefox for example. From the history https://openqa.suse.de/tests/15884559#next_previous we can see it failed every-time when the new build arrived and the build 36.1 is an exception. And it will pass after we restart the test.
In the https://openqa.suse.de/tests/15884559#settings we can see the x11-desktopapps-firefox should be run after create_hdd_gnome+we.
If we check the https://openqa.suse.de/tests/15884559/logfile?filename=autoinst-log.txt we can see the x11-desktopapps-firefox started at [2024-11-07T19:57:22.685258Z]
But for the parent job create_hdd_gnome+we, it started at [2024-11-07T20:17:55.196345Z] https://openqa.suse.de/tests/15883972/logfile?filename=autoinst-log.txt
That's the reason led to the x11-desktopapps-firefox ended up with incomplete status.
Updated by mkittler 10 days ago ยท Edited
- Status changed from In Progress to Feedback
The page of the corresponding scheduled product, e.g. https://openqa.suse.de/admin/productlog?id=2395203 tells you that the dependency was attempted to be created but that failed with create_hdd_gnome+we@64bit has no child, check its machine placed or dependency setting typos
.
It looks like such a job generally exists as part of the scheduled product, though: https://openqa.suse.de/tests/15883972
It is strange that the image creation job itself (even though it specifies not dependencies on its own) shows this error:
{
"error_messages": [
"create_hdd_gnome+we@64bit has no child, check its machine placed or dependency setting typos"
],
"job_id": [
15883972
]
},
However, the error message also gives you a good hint what the problem is. As it says, one should check the machine - and according to the documentation the MACHINE
is in fact tried to be matched as well:
To use it, simply append the machine name for each dependent test suite with an @ sign separated. If a machine is not explicitly defined, the variable MACHINE of the current job is used for the dependent test suite.
In this case no @
-syntax is used so it'll just use the MACHINE of the job. In case of the consuming jobs that is 64bit-2gbram
. In case of the job creating the image that is 64bit
. So there's a clear mismatch.
TLDR: I suppose the dependency creation would work if you'd explicitly specified the machine via the @
-syntax, e.g. START_AFTER_TEST=create_hdd_gnome+we@64bit
.
Updated by GraceWang about 23 hours ago
Sorry for the late feedback.
After changing to START_AFTER_TEST=create_hdd_gnome+we@64bit, everything works as expected.
Thanks a lot for your great help.