Repository navigation
Pop-B build-once fix (§1 floor cost): the ~16 already-#[ignore]'d subprocess/network tests are mostly (a)/(b) defects — ~6 rebuild the SAME stage0 binary per test instead of consuming the floor's prebuilt release bin. FIX: route them through the already-built binary (build-once / consume prebuilt re - #5450
Merged
Merged
Conversation
…ild_stage0 Six non-CI #[ignore]'d tests (strict_compile_diagnostic_count, stage0_compile_accepts_dag_target, stage0_compile_imports_ephemeral_generated_source_root, bootstrap_stage0_to_stage1, bootstrap_fixed_point, performance_ratchet) called build_stage0() directly, running `cargo build -p v1-compiler --release` once per test even when the floor's prebuilt release binary was already present. Route them all through find_or_build_stage0(), which checks for the prebuilt binary first and only rebuilds if absent. Also extract prebuilt_stage0_path() so the binary location logic (including CARGO_TARGET_DIR) is the single authority used by both the prebuilt-check and build_stage0() itself. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
briansrls
force-pushed
the
session/warm-ram-537
branch
from
June 21, 2026 06:59
0b26e83 to
8c0ec98
Compare
4 tasks done
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…-PR; no expensive-selector) Operator re-scope via quick-ant-298 on the opt-level-won trigger. Drop the expensive-category selector + Pop-A conversion list; narrow to the irreducible Pop-B residue (live-network core locked: interp_recorded_fixture + anthropic_live_e2e; cargo-check-on-emitted gray-zone + ci_ set pending warm-ram #5450 build-once drain confirmation). cfg_attr mechanism + separate nightly.yml + drift gate unchanged. CI-gen diff still escalated before landing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
Residue final: 2 live-network + 5 emitted-cargo (w/ dissolution trigger to drain to per-PR if an in-process emitted-Rust-wellformedness check replaces the cargo subprocess) + 5 ci_ ratchets. #5450 drains stage0-build-only (bootstrap 307/331/374/659); opt-level drains in-process (pipeline 8273/8291/10333/21). Sequencing step-1 (residue confirm) DONE; machinery diff still escalates before landing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
… cron wiring + nightly.yml §2-horizontal generalization (no forked 2nd emitter): expected_workflow_yml(workflow) is the ONE emit authority; expected_ci_yml/expected_nightly_yml are two wrapper rows. ci_yaml_gate is ONE gate concept over (path, expected, label); CiYamlGate + nightly are two instances. Schedule trigger cron projection wired (workflow_yaml_project.dag :94 YamlNull drop -> render_cron_schedule). nightly_workflow value (Schedule 0 7 * * * + workflow_dispatch, --features ci_nightly run step); ci_nightly feature declared in v1-compiler-tests (markings held for post-#5450). Floor-enrolled NightlyYamlGate witness (nightly_yaml_serializer_witness_test.dag). Proofs by execution (parent escalation packet): 1. ci.yml BYTE-IDENTICAL post cron-fix + prelude-factoring: CiYamlGate main=ExitSuccess, git diff HEAD ci.yml empty, existing ci_yaml serializer keystone still true. 2. cron renders by execution: pre-fix YamlNull -> witness RED + schedule block has no cron (3102 bytes); post-fix -> - cron: 0 7 * * * (3124 bytes), witness GREEN (discriminating). 3. NightlyYamlGate floor-enrolled (*_test.dag test fn) GREEN on committed, RED on perturbed; nightly.yml == expected_nightly_yml() byte-exact (nightly_main=ExitSuccess). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-opened by session-dashboard for session
warm-ram-537.Pushing to
session/warm-ram-537advances 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