Skip to content

ci: spec-guards print first compiler error when score = 1000000 - #14066

Merged
gHashTag merged 1 commit into
masterfrom
fix/spec-guards-error-13977
Nov 16, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/spec-guards-error-13977

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

What

Modifies the score() function in the "Affected specs" step to surface the
first error: line from t27c when a spec scores 1000000 (does not build).

Before: The step prints specs/foo.t27: head 1000000, base 0 with no
further detail. Finding the root cause required a manual lab run.

After: The step also emits:

  compiler: error: use of undeclared identifier `op_arena_len`

to stderr before the score line, visible in the CI log without leaving GitHub.

How

  • Add 2>&1 before the awk pipe so stderr is merged into the stream.
  • awk captures the first error: line in err.
  • When BLOCKED, awk prints compiler: <err> to /dev/stderr.
  • h=$(score "$f") still captures only the numeric score (stdout unchanged).

One line changed, net 0 additions. No behavior change when the spec builds.

Refs #13948. Closes #13977.

🤖 Generated with Claude Code

#13977)

Merge stderr into the awk stream and emit the first `error:` line to stderr
when a spec is BLOCKED. The score returned to `h=$()` is unaffected (stdout
only). Developers now see the root cause without a separate lab run.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) November 16, 2026 08:58
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-16 08:59:36 UTC

Summary

Status Count
Total Open PRs 46
PRs with Failing Checks 44
PRs with All Checks Green 2
READY 0
FAILING 44
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 44 + 0 + 0 = 44, and there are 46 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=29c50ada25c9 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 67dc5af into master Nov 16, 2026
32 of 34 checks passed
@gHashTag
gHashTag deleted the fix/spec-guards-error-13977 branch November 16, 2026 08:59
gHashTag added a commit that referenced this pull request Nov 16, 2026
…3957)

Absorbs 5 master commits (incl. #14065/#14066/#14069 lane merges). No
conflicts; keeps the keystone's merge-preview current for review.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: spec-guards Affected specs - print the compiler error of a spec that does not build

1 participant