| Summary: | Improve patchtest runtime | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Trevor Gamblin <tgamblin> |
| Component: | Patchtest | Assignee: | Trevor Gamblin <tgamblin> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | randy.macleod |
| Version: | 5.0 | ||
| Target Milestone: | 5.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Trevor Gamblin
2023-10-27 12:00:06 UTC
The reason that this is happening is because patchtest uses tinfoil to figure out which files have been added/modified/deleted/etc. in a given patch/series. The runtime impact of this can be reduced for now by using BB_SERVER_TIMEOUT = "60" in local.conf for patchtest runs (this has been implemented on my local selftest runs). For now, I think this is sufficient, as more significant patchtest adjustments will find newer ways to determine what files are changed. Closing for now, but it can be reopened if necessary. |