Commit ae8224e
committed
build,gate: fix stale getbuildinfo + ARM64 transcript truncation
Two latent build/gate-infra bugs surfaced during push 40 validation
(both unblocked the BINARY_MATCH fix from ab80360 to actually work
in practice):
1. scripts/build_phoenix.sh: rm -f Modules/getbuildinfo.o before
each build. The .o embeds GITVERSION/GITTAG/GITBRANCH at compile
time via -DGITTAG=`git describe --dirty`, computed AT FIRST BUILD.
Incremental rebuilds skip recompiling that .o (the .c is unchanged),
so once a binary is built dirty, every subsequent rebuild inherits
the '-dirty' marker forever — and the new BINARY_DIRTY check then
spuriously fails clean working trees. Forcing the .o to regenerate
each build re-evaluates the git describe at every compile.
2. scripts/gate_phoenix.sh: prefix the local nbs-remote-run call
with stdbuf -oL -eL. Two ARM64 truncation incidents during push
40 (01:11Z, 01:25Z) cut the gate transcript off mid-build, leaving
verdict undeterminable and forcing manual SSH verification. The
buffering happens on the LOCAL capture side ($(nbs-remote-run...)),
not on the remote — so stdbuf is applied to the LOCAL process, not
the remote heredoc.
Per supervisor 2026-04-22 01:27:22Z (bundling both into one push 41
infra batch) + librarian 01:27:02Z (stdbuf recommendation).1 parent ab80360 commit ae8224e
2 files changed
Lines changed: 15 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
176 | 176 | | |
177 | 177 | | |
178 | 178 | | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
179 | 187 | | |
180 | 188 | | |
181 | 189 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
531 | 531 | | |
532 | 532 | | |
533 | 533 | | |
534 | | - | |
| 534 | + | |
| 535 | + | |
| 536 | + | |
| 537 | + | |
| 538 | + | |
| 539 | + | |
| 540 | + | |
535 | 541 | | |
536 | 542 | | |
537 | 543 | | |
| |||
0 commit comments