| Summary: | 'Picky' builds should be assigned to workers first | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Richard Purdie <richard.purdie> |
| Component: | autobuilder | Assignee: | Trevor Gamblin <tvgamblin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | infras.ab.watcher, Infras.watcher, pidge, randy.macleod, tim.orling, tvgamblin |
| Version: | 3.1 | ||
| Target Milestone: | 4.0 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2019-11-21 20:29:17 UTC
Also, it seems if the next build requires a specific worker, there are times this seems to block any further builds being run until one is available. Patch is on yocto-autobuilder2 master: http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder2/commit/?id=b5a047f99f60595372aaeda9de9400801c83e7f2 Will be tested after the controller is restarted tomorrow. Marking this as done since it's been in use for a little while now (with the addition of some extra patches from Richard). |