Skip to content

spec(t27os): an identical t27b leg on redispatch is a success, not a red (Closes #12293) - #12294

Merged
gHashTag merged 1 commit into
masterfrom
night/165-t27b-publish-idem
Oct 25, 2026
Merged

gHashTag merged 1 commit into
masterfrom
night/165-t27b-publish-idem

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Closes #12293. Refs Trinity-S-AI-DNA/t27os#3.

The t27b leg file is named by the sha alone (runs/<sha>.t27b.txt), so a lab redispatch of a sha writes the same bytes t27os master already holds. git add stages nothing, and the bare git commit exits 1 under bash -e. Lab run 40166771453 (68899a6, second dispatch) went red that way after both its tests and the t27b leg had passed. Night tick 157 hit the same red.

  • SAME_LEG = git diff --cached --quiet && exit 0 now stands before the staging commit and again before the commit on fresh master (a racing publisher can land the same bytes between the two).
  • T27B_PUBLISH_40166771453 keeps the measured step as the negative control.
  • New test an_identical_t27b_leg_is_a_success_not_a_red; publish_ok still holds.

Verification

  • t27c per-test report: 6/6 pass, 0 vacuous (new test: 6 runtime asserts).
  • t27b: the t27os lab leg is queued after the run in flight. This PR stays a draft until the receipt runs/74dc739e78*.json shows it green.

After merge, TRI CLAW (or a night tick) copies the new step text into t27os lab.yml.

🤖 Generated with Claude Code

…red (Closes #12293; Refs Trinity-S-AI-DNA/t27os#3)

The t27b leg file is named by the sha alone, so a redispatch writes the
bytes t27os master already holds; `git add` stages nothing and the bare
`git commit` exits 1 under bash -e. Lab run 40166771453 (68899a6,
second dispatch) went red that way after its tests passed.

SAME_LEG (`git diff --cached --quiet && exit 0`) now stands before the
staging commit and before the commit on fresh master. The step of run
40166771453 is kept as the negative control. t27c: 6/6, 0 vacuous.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-25 06:19:18 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 39
PRs with All Checks Green 11
READY 5
FAILING 39
PENDING 0
NO CHECKS YET 0

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=55c0f1b1b32d != 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).

This was referenced Oct 25, 2026
@gHashTag

Copy link
Copy Markdown
Collaborator Author

Night tick 172: lab dispatched on 74dc739 (run 40173880388, challenge d07dd24b2baee034, specs/t27os/lab_publish.t27). Receipt lands at Trinity-S-AI-DNA/t27os runs/74dc739e7825c21529d1650ce7d4ab3fd2cd8888.*.json.

@gHashTag

Copy link
Copy Markdown
Collaborator Author

Lab receipt (night tick 175): Trinity-S-AI-DNA/t27os runs/74dc739e7825c21529d1650ce7d4ab3fd2cd8888.79ce3da9.json, run 40173880388.
t27c leg: specs/t27os/lab_publish.t27 tests=6 pass=6 FAIL=0 vacuous=0 blocked=0 (ok=true, asked 1, reported 1).
t27b leg: job still running at 08:16Z; undraft waits for it.

@gHashTag

Copy link
Copy Markdown
Collaborator Author

Lab t27b leg (night tick 176): Trinity-S-AI-DNA/t27os runs/74dc739e7825c21529d1650ce7d4ab3fd2cd8888.t27b.txt (commit f1f5f80), run 40173880388.
t27b leg: specs/t27os/lab_publish.t27 tests=6 pass=6 FAIL=0 vacuous=0 asserts=29
t27c leg (receipt 79ce3da9): tests=6 pass=6 FAIL=0 vacuous=0 blocked=0
Both compilers green on this head; undrafting.

@tri-claw

tri-claw Bot commented Oct 25, 2026

Copy link
Copy Markdown

Summary by t27-bees

Checked by the t27 compiler

t27c parse, parse-complete and typecheck on each changed .t27 file at 74dc739. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/t27os/lab_publish.t27: parses and typechecks.

Read by the model

The change adds a git diff --cached --quiet && exit 0 guard in two places in the t27b publish step so that a redispatch writing an identical leg file (named by SHA alone) succeeds instead of failing on "nothing added to commit" under bash -e. The guard appears before the staging commit and again in the retry loop on fresh master to handle a racing publisher landing the same bytes between the two commits.

Worth a look

  • specs/t27os/lab_publish.t27:58 — The first SAME_LEG guard exits the entire step with success when git add stages nothing. If the runner's HEAD already has the leg file (e.g., from a prior partial run), the step succeeds without ever verifying the file is actually on origin/master. The second guard in the retry loop covers the race, but the first guard may declare success against a stale local HEAD.
  • specs/t27os/lab_publish.t27:67 — The second SAME_LEG guard runs after git checkout "$rcpt" -- runs/<sha>.t27b.txt on a fresh origin/master. If the checkout stages the file (because it differs from master) but the content is byte-identical to what master already has, git diff --cached --quiet correctly returns 0 and exits success. However, if the checkout stages nothing because the file is already present in the working tree from a previous loop iteration, the guard would also exit success — but the loop re-creates the branch each iteration (-B receipt), so the working tree is clean at that point.
  • specs/t27os/lab_publish.t27:123–135 — The new test asserts exact string containment including newlines and indentation. If the YAML template is reformatted (e.g., different indentation in the heredoc), the test will fail even if the semantics are unchanged.

Read: 1 files, +25 -1, the whole diff. Head 74dc739. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@gHashTag
gHashTag merged commit 730a9f3 into master Oct 25, 2026
38 checks passed
@gHashTag
gHashTag deleted the night/165-t27b-publish-idem branch October 26, 2026 03:42
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.

t27os lab: an identical t27b leg on redispatch turns the publish step red

1 participant