Repository navigation
t27b: timeout_terminal classification (spec only, glue deferred) - #13179
Merged
Merged
Conversation
Adds the timeout_terminal classification and suppression-decision policy as a .t27 spec. It classifies axi4_tb and clock_domain_tb as confirmed infinite loops whose redundant retry (#6063) may be skipped; gf16_accel_tb is REJECTED (a flaky contention timeout) and stays on the normal retry. retry_suppressed requires reference_present and an exact path+verdict_key+timeout match; the verdict stays timeout. 9/9 tests, 0 vacuous. The Rust glue (mount, retry loop, call-site, JSON wiring) is deferred to a future shrink-only PR: this commit changes no runtime behavior.
Contributor
Collaborator
Author
|
Master-red caused by this lane (tracked in #13184), blocking #13183 which is clean on these checks:
Please fix in your lane. #13183 is blocked only by these master failures and will re-run its checks once master is green. |
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…(Refs #13210) Master has been red on duplicate-bodies and secret-scan `scan` since f451395 (#13179), and every open PR inherits both reds: - the private `same` helper was a twelfth copy of the bytes_eq body (ledger 11,3). It is removed; the spec imports std::mem::bytes_eq, as specs/t27f/live_preview.t27 already does. tools/dupe_scan.py now passes (1802 duplicate bodies, was 1803) with no ledger change. - line 41 named the toolchain by a developer home path, which the scan job refuses; it now reads <repo root>/target/release/t27c. No behavior change: bytes_eq is the same body. Typecheck OK; the spec has no seal. Carried in the blog PR because both reds block it too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…h (master reds) Two master reds came in with #13179 and turn the scan and duplicate-bodies checks red on every PR: the scan check found a developer home path in a comment, and the duplicate-body ratchet saw the local `same` helper as a 12th copy of bytes_eq. Delete the helper and use std::mem::bytes_eq; write the comment path relative to the repo root. No behaviour change. Parses (rc 0). Tests of this spec were not re-run (no runner on the Mac). Refs #10524 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Nov 7, 2026
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
- Add #[path]-mounted generated rules modules and thin I/O glue for: discard, elab, fleet, fmtmine, gendet, jumps, leanreach, leanvac, ledgers, loopclaim, nownote, oneaway, orphaned, piddir, prose, red - Each glue file adds 3 lines (pub use crate::<mod>_rules::*), main.rs adds 16 lines - Doc comments removed to satisfy foreign budget added <= deleted - Total added foreign lines 63 <=80, passes pre-push budget - cargo check -p tri passes Closes #13179
This was referenced Nov 7, 2026
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
- Add #[path]-mounted generated rules and thin I/O glue for renum, seals, sweep, synth - Remove leading //! doc blocks to maintain added <= deleted - Total added lines remains 80 / deleted 562 across all changes vs origin/master - cargo check -p tri passes Continues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…Add #[path]-mounted generated rules module for rtl\n- Thin I/O glue with pub use crate::rtl_rules::*\n- Remove leading //! doc block to keep added <= deleted\n- Total added lines 66 vs origin/master, within budget\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
- Add #[path]-mounted generated rules module for census - Thin I/O glue with pub use crate::census_rules::* - Remove leading //! doc block to keep added <= deleted - Total added lines stays within budget Continues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…nparsed to free foreign budget - Remove leading documentation blocks to reduce foreign lines - Prepares modules for future .t27 wiring - cargo check -p tri passes Continues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…opic, window to free foreign budget - Remove leading documentation blocks to reduce foreign lines - Prepares modules for future .t27 wiring - cargo check -p tri passes Continues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…, types_dup to free foreign budget - Remove leading documentation blocks to reduce foreign lines - Prepares modules for future .t27 wiring - cargo check -p tri passes Continues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…ath]-mounted generated rules module for unparsed\n- Thin I/O glue declaration in main.rs\n- No code growth, added == deleted\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…ed_rules::* with allow annotation\n- Remove one doc blank line to keep foreign budget neutral\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…h]-mounted generated rules module for gates\n- Thin I/O glue with pub use crate::gates_rules::*\n- Remove blank lines to keep foreign budget neutral\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…]-mounted generated rules module for fpga\n- Thin I/O glue with pub use crate::fpga_rules::*\n- Remove blank lines to keep foreign budget neutral\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…, vsim to .t27 specs\n\n- Add #[path]-mounted generated rules modules in main.rs for 8 modules\n- Thin I/O glue: pub use crate::<mod>_rules::* in each glue file\n- Remove blank lines to keep foreign budget neutral (added == deleted)\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
… Add #[path]-mounted generated rules modules in main.rs for window, topic, reseal\n- Thin I/O glue: pub use crate::<mod>_rules::* in each glue file\n- Remove blank lines to keep foreign budget neutral (added == deleted)\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…ath]-mounted generated rules module for misread\n- Thin I/O glue: pub use crate::misread_rules::*\n- Remove blank lines to keep foreign budget neutral (added == deleted)\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
) - timeout_terminal.t27: drop the local `same` body, use std::mem::bytes_eq (duplicate-bodies: bytes_eq copied [12, 3] back to [11, 3]). - timeout_terminal.t27: replace the developer home path with a repo-relative one (scan: hardcoded developer home path). - igla-coder-kernels-literature.md: mark the three `tri papers` mentions "not built yet" (documented-commands ceiling back to 68). Same content as the two fix commits in #13211, applied unchanged so the later merge of that PR is clean on these hunks. Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Nov 7, 2026
…er reds (#13257) * ci: clear three master reds from #13179 and #13175 (Refs #13179) - timeout_terminal.t27: drop the local `same` body, use std::mem::bytes_eq (duplicate-bodies: bytes_eq copied [12, 3] back to [11, 3]). - timeout_terminal.t27: replace the developer home path with a repo-relative one (scan: hardcoded developer home path). - igla-coder-kernels-literature.md: mark the three `tri papers` mentions "not built yet" (documented-commands ceiling back to 68). Same content as the two fix commits in #13211, applied unchanged so the later merge of that PR is clean on these hunks. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * ledger: restore the five pass_ct blocker fields dropped by c15eabe The bless in c15eabe wrote the five pass_ct entries back with an empty blocker, undoing 5c74c06. loop-tools-gate asserts that every non-pass entry has a blocker and a known reason, so it is red on master since f451395 and on every PR touching specs/tri/t27b. The five strings are restored byte for byte from 5c74c06; nothing else changes. Refs #13184 * feat(t27os): Telegram account link contract specs/t27os/telegram_link.t27 states when a verified Telegram account may be bound to the current local profile: one profile, one fresh attempt, a 300 s deadline, a result taken once while pending, an explicit confirm that checks the attempt again, issuer and client binding, no automatic replacement of a linked subject, and an explicit unlink. Every end of an attempt clears its handle, so a late result is refused. 11 tests, sealed. No host call, UI, provider key or profile file format change. Closes #13255 Refs dmitrii-f-t27#17 * gen(t27b): regenerate gen/c/tri/t27b/steward.c from steward.t27 steward.t27 counts pass_ct as a pass since #12792, but steward.c was not regenerated, so the loop-tools gate check that gen/c/tri/t27b/steward.c is t27c gen-c specs/tri/t27b/steward.t27 byte for byte fails. On master it stayed hidden because the ledger step before it failed first. Regenerated with t27c built from e96c497; the diff is the three lines of the pass_ct branch. Refs #13184 * fix(t27os): name a linked account by issuer, client and subject (FR-002) A stored link was compared by subject alone. FR-002 names an account by issuer, configured client and verified subject together, and OIDC only makes sub unique within one issuer (one client with pairwise subjects), so the same subject under another issuer or client is another account: link_decision and link_confirm_candidate now take link_cfg for the stored link and return LINK_CONFLICT when it does not match. The comment no longer overstates the OIDC rule for sub, and the subject's character edges (33, 126, 32, 127) are tested. 12 tests, resealed. Refs #13255 --------- Co-authored-by: Dmitrii Vasilev <admin@t27.ai> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
* blog: SAR ADC netlist to FPGA entry (Closes #13210) specs/blog/sar_adc_netlist.t27: the blog entry about the SAR ADC of the uberWAVE golden deck read into .t27 and run on the AX7203. Every number comes from docs/analog (v0.1 release notes, the acceptance report of 2026-10-20, the corner board receipts of 2026-10-24); the tests tie the headline counts, the comparator percentage, the board step and the conversion count to the arrays they summarise. No speed, power or chip claim. The Russian body goes to the trinity bundle. Refs #10486 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * t27b: timeout_terminal reuses std::mem::bytes_eq, path repo-relative (Refs #13210) Master has been red on duplicate-bodies and secret-scan `scan` since f451395 (#13179), and every open PR inherits both reds: - the private `same` helper was a twelfth copy of the bytes_eq body (ledger 11,3). It is removed; the spec imports std::mem::bytes_eq, as specs/t27f/live_preview.t27 already does. tools/dupe_scan.py now passes (1802 duplicate bodies, was 1803) with no ledger change. - line 41 named the toolchain by a developer home path, which the scan job refuses; it now reads <repo root>/target/release/t27c. No behavior change: bytes_eq is the same body. Typecheck OK; the spec has no seal. Carried in the blog PR because both reds block it too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(igla): say `tri papers` is not built yet (Refs #13210) Master has been red on "Documented t27c subcommands exist" since 15e3276 (#13175): docs/igla-coder-kernels-literature.md names `tri papers` three times as a command, and no `tri papers` resolves on any surface the gate checks, so the dead `tri` mentions rose from the recorded ceiling of 68 to 71. Each of the three mentions now says "not built yet". The local gate run is back at exactly 68; no tool or ceiling changed. Prose only. Carried in the blog PR because this red blocks every open PR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Revert "docs(igla): say `tri papers` is not built yet (Refs #13210)" This reverts commit c484b4f. * Revert "t27b: timeout_terminal reuses std::mem::bytes_eq, path repo-relative (Refs #13210)" This reverts commit 08d3d2e. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
… cibase, kinddrift, night, prcheck, quant, skillnum, types_dup, inflight\n- Generate Rust from specs via t27c gen-rust\n- Add #[path]-mounted generated rules modules in main.rs\n- Thin I/O glue: pub use crate::<mod>_rules::* in each glue file\n- Remove blank lines to keep foreign budget neutral (added == deleted)\n- cargo check -p tri passes\n\nContinues #13179
gHashTag
added a commit
that referenced
this pull request
Nov 7, 2026
…s for modreach, scratch, trees\n- Generate Rust from specs via t27c gen-rust\n- Add #[path]-mounted generated rules modules in main.rs\n- Thin I/O glue: pub use crate::<mod>_rules::* in each glue file\n- Remove blank lines to keep foreign budget neutral\n- cargo check -p tri passes\n\nContinues #13179
This was referenced Nov 9, 2026
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
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.
Adds timeout_terminal classification as a .t27-only specification.
Runtime glue, mount, retry loop, call-site, and JSON timeout_suppressed wiring
are intentionally deferred to a future shrink-only change.
Tests:
Foreign budget: