action #157342
opencoordination #154768: [saga][ux] State-of-art user experience for openQA
coordination #157345: [epic] Improved test reviewer user experience
Partial product re-scheduling scheduled whole build
0%
Description
We have development group for 15-SP6 Online x86_64 architecture https://openqa.suse.de/group_overview/507.
There was missing HDD_1 and job failed https://openqa.suse.de/tests/13783898/modules/boot_to_desktop/steps/4.
We fixed the configuration and we clicked on Parial product re-scheduling:
It should re-schedule partially, at least this is our understanding of help description.
Unfortunately, it rescheduled whole x86_64 medium for 15-SP6 Online.
It is either bug in the re-scheduling code or help description is wrong. User has expectation (based on help) that re-schedules only his job and its children or that job group.
Could you please investigate it ?
Files
Updated by acervesato 4 months ago
In my opinion, it makes sense to threat it as a bug, considering how clear it is the help documentation on that specific feature. It's kinda awkward that by scheduling a single job we affect a chain as a whole and other people work as well.
Updated by okurz 4 months ago
- Related to action #138593: Restart of scheduled products is prone to retriggers by humans size:S added
Updated by mkittler about 1 month ago
Without knowing the dependency tree of the specific job it would involve a lot of guesswork to work on this.
Note that the partial re-triggering feature was designed to decide what re-schedule based on job dependencies (as I suppose this was the initial requirement for the feature). So it is expected that it doesn't stop at job group boundaries if the dependency tree contains jobs across different job groups.