| Summary: | Random package/image builder (fuzzy build) | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Beth Flanagan <elizabeth.flanagan> |
| Component: | autobuilder | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, california.l.sullivan, elizabeth.flanagan, infras.ab.watcher, Infras.watcher, jessica.zhang, sgw |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Beth Flanagan
2014-05-07 22:18:15 UTC
Recipe-specific sysroots have probably solved most of the issues that would have been brought to the surface by this, since it should not be possible for missing dependencies to lead to non-deterministic behaviour anymore. I also have to say I am very skeptical of randomness in running builds for CI or testing purposes - there's a chance that you will miss running a portion of the tests regularly enough. If it were needed due to the time taken to run the full set, it suggests that we aren't providing enough resources to run the tests and/or we need to optimise what we are testing (in a targeted manner). |