feat(local): classify failing binary builds and pre-fill registry suggestions #116
Loading…
Reference in a new issue
No description provided.
Delete branch "t3code/missing-package-binaries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements steps 1 + 2 of #115: turn recorded build failures into triaged patch suggestions instead of hand-scraping Crow logs.
What this adds
A read-only reporting pipeline over the
single_buildsmetadata table. It never writes to the DB or the registry.local/failing-builds-classify.R— pure, DB-free helpers:normalise_error()strips temp paths, version numbers, hex addresses, and the package name so the same root cause collapses to one fingerprint.fingerprint_error()extracts the salient error line and normalises it.classify_error()matches against a seed signature set; unmatched errors are never guessed at.propose_registry_entry()renders a schema-validregistry.jsonentry.local/failing-builds-report.R— entrypoint: queriessingle_builds WHERE error_occurred = TRUE AND removed = FALSE, groups by root cause (signature when classified, fingerprint otherwise), classifies each group, and prints a triaged report. Flags:--platform,--arch,--min,--json;PLATFORM/ARCHenv fallbacks.local/tests/test-failing-builds-classify.R— unit tests for the helpers.local/patches/README.md— documents the workflow.Seed signatures
Each rule carries a fix tier, confidence, and an auto/human-only flag:
tbb/tbb_stddef.h: No such file-DTBB_INTERFACE_NEWdisable-tbb.patchlibuv.solink leakGuardrails honored
src/contribindex.single_builds.error_text; no new failure-capture pipeline.Verification
air-format,validate-patches, prettier, etc.).local/validate-patches.R.Steps 3 (auto-open PRs) and 4 (feedback loop) are intentionally deferred, per the issue's suggestion to validate the signature set first.
Closes #115