Identify directly failed builders in rejected updates #2
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/failed-builder-attribution"
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?
Rejected-update evidence counted build-plan and dependent derivations as failed packages, so a single Moonlight compilation failure was incorrectly treated as multiple failures and excluded from remediation. Extract only explicit failed-builder diagnostics, including legacy/modern Nix output and fixed-output hash mismatches; retain multiple independent roots as ineligible.
Refs nimmo/nixos-config#208.
Validation: incident protocol regressions, ShellCheck and formatting passed. A real failing leaf/dependent Nix probe identified only the leaf; the historical Moonlight/FFmpeg candidate reproduced its compiler failure and emitted exactly one Moonlight culprit. Configuration/controller integration and full flake validation were exercised with this helper. No deployment or merge performed.
nimmo referenced this pull request from nimmo/nixos-config2026-09-09 18:23:33 +01:00