Skip to content

t27c test: execute assertions via zig test (Closes #11805) - #11806

Merged
gHashTag merged 5 commits into
masterfrom
fix/t27c-test-executes-11805
Oct 27, 2026
Merged

gHashTag merged 5 commits into
masterfrom
fix/t27c-test-executes-11805

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

run_test now generates Zig and runs zig test when the generated Zig compiles; non-compiling specs keep the legacy declaration-only result. False assertion -> exit 1; passing -> exit 0. 25 lines added (<=40/file). Closes #11805. Refs #11730.

@tri-claw

tri-claw Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Summary by t27-bees

The change makes run_test generate Zig code from the parsed AST and execute it via zig test to actually run assertions (compile-check with --test-no-exec, then full execution). Non-compiling specs silently fall back to the old declaration-only behavior.

Worth a look

  • bootstrap/src/main.rs:11094-11110 — Temp file path std::env::temp_dir().join("t27_test.zig") is fixed; concurrent run_test invocations will race/overwrite each other's input. No cleanup of the temp file after use.

  • bootstrap/src/main.rs:11103 — tmp.to_str().unwrap_or("") passes an empty string to zig if the temp path contains non-UTF-8 sequences, causing a confusing compiler error instead of a clear failure.

  • bootstrap/src/main.rs:11095-11099 — Parse or codegen failures (compiler::Compiler::parse_ast error, codegen.gen_zig panic, or fs::write error) are silently swallowed and fall through to Ok(()), preserving legacy "declaration-only" success for broken specs. This masks real problems.

  • bootstrap/src/main.rs:11101-11105 — No timeout on zig test; a hanging test (infinite loop, deadlock) blocks the process indefinitely.

  • bootstrap/src/main.rs:11101-11105 — Assumes zig is on PATH and supports --test-no-exec; no version check or fallback, so environments without Zig or with older versions will fail mysteriously.


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

@gHashTag

Copy link
Copy Markdown
Collaborator Author

🔬 The T27 OS lab (workflow_dispatch, t27os repo — no Railway) was dispatched on this PR's head with its touched specs. The receipt lands in Trinity-S-AI-DNA/t27os runs/<sha>.*.json — read it before merging; a red line there is a real finding, not noise (the lab's wasm32 step caught a sha256 defect on master tonight — epic #11840).

This was referenced Oct 27, 2026
@gHashTag

Copy link
Copy Markdown
Collaborator Author

; OWNER DECISION NEEDED (own-language net +10): the fix works and is verified end-to-end (compact 14-line runner: failing assert -> 'zig test failed', passing -> OK; build 0 errors), but the PR diff stays net +10 after the honest compressions -- the rest of the honest cut would gut the memory-comments of run_test's neighbours (debug histories, contracts). Two clean paths: (a) owner-approved-foreign label on this PR, or (b) the author re-lands via the budget_discipline recipe (specs/policy/budget_discipline.t27). A verified local branch (wip/11806-compact, patch saved on the session side) carries the compacted version either way.

…s compressed to their facts, net of the discipline honored (Refs #11805)
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-27 11:21:38 UTC

Summary

Status Count
Total Open PRs 9
PRs with Failing Checks 6
PRs with All Checks Green 3
READY 2
FAILING 6
PENDING 0
NO CHECKS YET 0

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e75b498e5e79 != 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 0463ab7 into master Oct 27, 2026
29 of 38 checks passed
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.

t27c test: execute assertions, not just count declarations (t27#11730)

2 participants