Project

General

Profile

Actions

action #45749

closed

[tools][scheduler] Multi-machine jobs with higher priority do not get worker to run.

Added by xlai over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-01-07
Due date:
% Done:

0%

Estimated time:

Description

During 15sp1 beta1 test, the multi-machine jobs(2 sut) in virtualization job groups can not get workers to kickoff job until some low priority single machine jobs finish. This delays especially acceptance test(not able to finish within 24 hours).

https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=125.1&groupid=115
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=125.1&groupid=213

I did not open a ticket when I found it, because I understood that:
although they were with higher priority in our group, but possibly other job group ipmi jobs have even higher priority. So they got the machine first, and they did not finish at the same time, so our multi-machine jobs still could not be started and other lower priority single machine jobs started.

@okurz commented that openqa tool should make some enhancement for it in https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/148/.

Please help to evaluate. Really appreciate.

Actions

Also available in: Atom PDF