Skip to content

Show why a unit failed at each step of a bisection - #248

Merged
tamnd merged 2 commits into
mainfrom
unit-why
Oct 9, 2026
Merged

tamnd merged 2 commits into
mainfrom
unit-why

Conversation

@tamnd

@tamnd tamnd commented Oct 9, 2026

Copy link
Copy Markdown
Owner

A unit bisection prints only builds or fails for each commit, and it deletes its scratch tree, so a commit where the object fails for some other reason looks the same as one that fails for the reason being bisected. That happened to the bisection of binutils-too-old-multiline-macro, from 2.6.22 to 2.6.23 with GCC 3.2.3 and binutils 2.14 on x86_64. It reported that arch/x86_64/kernel/head.o fails at 2.6.23 as well, even though 6e3515352bdd puts the PMDS() call back on one line in v2.6.23-rc4. Nothing was left to show why.

unit_rung now also returns the first line of unit.log, or of prepare.log when prepare is what failed, that names an error. If no line does, it returns the last line where kbuild says why it stopped. The line is taken before the scratch tree goes, and it is printed under the step, the same way the first error of a whole-cell step already is.

New test: a_failed_unit_says_what_failed. fmt and clippy are clean on server3 and all 131 tests pass.

@tamnd tamnd added this to the G2: the modern history milestone Oct 9, 2026
@tamnd tamnd added kind/feature New capability in gk or the pipeline area/gk The gk command line and model crates area/search Frontier search, sampling and sweeps priority/p2 Should land in the current milestone labels Oct 9, 2026
@tamnd
tamnd merged commit 284058f into main Oct 9, 2026
2 of 3 checks passed
@tamnd
tamnd deleted the unit-why branch October 9, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/gk The gk command line and model crates area/search Frontier search, sampling and sweeps kind/feature New capability in gk or the pipeline priority/p2 Should land in the current milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant