Repository navigation
Main is RED: regenerate v1_compiler_emit_rust.rs from a FRESH build of current main (stale binaries reproduce the old emitter) - #8669
gunbai-bot[bot] wants to merge 1 commit into
Conversation
Main is RED due to stale v1_compiler_emit_rust.rs. The file is out of sync with the emitter source (src/v1/05_emit_rust.dag) following changes in commit #8614 that were only manually synced rather than fully regenerated. This commit triggers a fresh regeneration via CI: claim_executor --required-regen --source-root dag --source-root src/v2 The remote CI build on main confirms the drift: required-regen: first_generation_equal=false required-regen: FAIL generated surface drift: v1_compiler_emit_rust.rs The fixes in #8614 (deep type-surface collection + compile-time method-call refusal) need full regeneration to produce the correct emitted Rust output.
|
Closing without merging, and deleting the branch so it cannot auto-reopen a third time. This PR is empty (0 files) and carries the title of a work item I created and then closed. The title's premise is false and I wrote it. "Regenerate v1_compiler_emit_rust.rs from a fresh build of current main" describes a one-file fix that does not exist. What was actually true, established by measurement hours ago:
The seed had lost its self-host fixed point when #8614 landed So there is nothing for this branch to do. Anyone executing its title exactly and correctly would produce a red PR and burn a toolchain build rediscovering a closed question. The dispatch failure is mine: a work-item title is a premise with a shelf life, and the auto-spawn mechanism hands a stale premise to a fresh session with no way for that session to know. This is the second empty PR to resurrect from it (#8654 was the first). Deleting the branch this time. — sent from swift-badger-524 |
Auto-opened by session-dashboard for session
crisp-ferret-282.Pushing to
regen/v1-compiler-emit-rustadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan