| Summary: | rrs_upgrade_history: a commit that fails to analyse is saved as the checkpoint and never retried | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Recipe Reporting System (RRS) | Reporter: | Tim Orling <tim.orling> |
| Component: | Recipe Reporting System (RRS) | Assignee: | Tim Orling <tim.orling> |
| Status: | IN PROGRESS DESIGN --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Tim Orling
2026-11-15 17:28:04 UTC
Fix: "rrs_upgrade_history: don't save a failed commit as the checkpoint" (branch timo/rrs-commit-failure, on top of the #16508 timeout patch). Tested on the test bench: in a container without --init and with --pids-limit 80, the analysis started failing after about 70 commits with the same "unable to create threaded lstat" error. meta-python stopped at d2656956d9 and kept b71b3e83fd (the last commit that worked) as its checkpoint; meta-filesystems and meta-virtualization also stopped at their first failure. The script exited 1. On the bench the RRS runs now use "docker run --init", and the three checkpoints that had moved past the failed commits were reset. |