Skip to content

t27b-lab: a lane request skips the fuzzer (Closes #8267) - #8268

Merged
gHashTag merged 1 commit into
masterfrom
t27b-lab-request-no-fuzz-8267
Oct 9, 2026
Merged

gHashTag merged 1 commit into
masterfrom
t27b-lab-request-no-fuzz-8267

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Closes #8267

Why

Lane PRs under #6063 / #6198 wait in the t27b-lab request queue for a signed run of their head. On 2026-10-09 three lanes and #8055 were waiting at once. The master run of 0fca4bd took 22 minutes:

step seconds
t27b_corpus 341
reference 328
fuzz 427
receipt 126

A lane request is judged by corpus-receipt compare on its receipt. The receipt does not carry the fuzzer's summary and no lane reads it, so a request run now skips the step: about 7 of its 22 minutes. Master runs keep the fuzzer.

Change

After merge

Redeploy the lab with railway up from a clean git archive of contrib/railway/t27b-lab, between two runs.

🤖 Generated with Claude Code

The fuzz step took 427 s of the 22-minute master run of 0fca4bd. A lane
request is judged by corpus-receipt compare on its receipt, which does not
carry the fuzzer's summary, so the step now runs only for master runs.
One line edited, net 0 hand-written lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) October 9, 2026 16:57
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-09 16:58:25 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 49
PRs with All Checks Green 1
READY 0
FAILING 49
PENDING 0
NO CHECKS YET 0

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=557cd271f4e3 != 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 0f66f5d into master Oct 9, 2026
25 of 26 checks passed
gHashTag added a commit that referenced this pull request Oct 10, 2026
… master, not the master last run (Closes #8785) (#8786)

lane_request() took the first-parent line of the master the lab LAST RAN, so a
squash commit that landed after that run read NOT_ON_ORIGIN until the next
master run, waited as WAIT_ORIGIN and was dropped once older than the grace
(6a7b774 on 2026-10-10). It now fetches origin's REF into
refs/remotes/origin/<REF> (the checkout does not move) and reads that ref's
first-parent line, plus the ls-remote heads. A failed fetch leaves the ref at
an older master, never at a lane sha, so on origin can only shrink.

lab.py: 6 lines rewritten, net 0. Requests still skip the fuzzer (#8268) and
up to two run per master run (#8588).

corpus_receipt.t27: the comments that said the lab judges on-origin against
the master it last ran are corrected, and a test pins the verdicts for a
squash newer than the last master run. request_verdict and request_exit do
not change. gen-rust regenerated and the seal re-saved (33 of 33) with
master's t27c on t27b-lab, after a control run reproduced master's file and
seal exactly.

Co-authored-by: Claude <claude@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

t27b-lab: a lane request skips the fuzzer (7 of 22 minutes per run)

2 participants