Test report¶
Note
Auto-generated from a live ctest run by bench/gen_test_report.py (regenerated in CI before every Pages deploy). Not hand-maintained.
Summary¶
suites |
passing |
conformance vectors |
wall time |
verdict |
|---|---|---|---|---|
287 |
287/287 |
99 |
144.31s |
✅ all green |
By subsystem¶
category |
suites |
passing |
|---|---|---|
Codec (L2/L3) |
15 |
✅ 15/15 |
Substrate (L0/L1) |
17 |
✅ 17/17 |
Graph (L4) |
24 |
✅ 24/24 |
Net (FWD plane) |
26 |
✅ 26/26 |
Transport |
9 |
✅ 9/9 |
Examples |
70 |
✅ 70/70 |
other |
126 |
✅ 126/126 |
Suites¶
Each row’s description is the test file’s own @brief, read from the source at generation time, and source links to that file. Neither is transcribed into this generator, so neither can drift from the test.
Codec (L2/L3)¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
Unit tests for the little-endian (de)serialization primitive (byteorder.hpp). |
|
|
✅ pass |
0.00s |
can_transport_t PURE framing-layer test (#55). |
|
|
✅ pass |
0.02s |
Conformance harness for the seed vectors under tests/conformance/vectors/v1/. |
|
|
✅ pass |
0.00s |
Frame-codec nesting + length-width tests. |
|
|
✅ pass |
0.00s |
Unit tests for tr::wire::key_view_t (key_view.hpp) — the canonical-key NAME navigation the L4 graph dispatch and ACL-inheritance walks funnel through. |
|
|
✅ pass |
0.00s |
length_prefix_framer_t unit test — drives the u32-length-prefix reassembly state machine directly (no QUIC connection), the whole point of extracting it from transport_quic / transport_webtransport (finding #4): prefix/body split across chunks, multiple frames per chunk, empty records, over the protocol cap => malformed, over local capacity => backpressure drain + resync (#932), and reset. |
|
|
✅ pass |
0.00s |
Differential test for the rope-aware grammar (ADR-0048 §1): wire::validate_rope over a scatter-gather rope MUST reach the exact same verdict as wire::decode over the equivalent flat bytes — for every adversarial split, including splits that fall mid-header, mid- trailer, and mid-payload. |
|
|
✅ pass |
0.08s |
Rope-source differential FUZZER for the wire grammar (ADR-0048 §consequences: “the differential fuzzers gain a rope-source mode — same bytes split at adversarial link boundaries MUST decode identically to the contiguous case, including mid-header splits”). |
|
|
✅ pass |
0.00s |
Terminus arena decoder test (ADR-0041). |
|
|
✅ pass |
0.00s |
The in-place TLV walker ( |
|
|
✅ pass |
0.00s |
Tests for the lazy rope-backed decode view (ADR-0053): tlv_view_t over a scatter-gather rope must (a) agree with the eager decoder node-for-node when fully walked, (b) be actually LAZY — siblings of a corrupt TLV deliver, the corrupt one fails only its own verify(), bytes are shared not copied — and (c) keep its links’ segments alive past the source rope (owning tier). |
|
|
✅ pass |
0.00s |
transport_ws PROTOCOL-layer test (#54). |
|
|
✅ pass |
0.63s |
RFC-0028 §6.9 / §9 item 6 — two publishes racing onto ONE WebSocket peer arrive as two whole frames, in order: no frame is torn by another frame’s bytes. |
|
|
✅ pass |
0.51s |
#934 car B — the WS OPENING HANDSHAKE is bounded by a deployment-injected pre-auth budget: an over-budget request is refused BEFORE it is buffered, counted, and closed. |
|
|
✅ pass |
1.25s |
#872 — the WS DATA path is bounded by the injected seam: a peer may not name the receiver’s memory budget, and every refusal is COUNTED. |
Substrate (L0/L1)¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
Unit tests for the bounded RECYCLING block source ( |
|
|
✅ pass |
0.00s |
Unit tests for the nothrow failable-block seam (mem_source.hpp, #551). |
|
|
✅ pass |
0.00s |
The |
|
|
✅ pass |
0.00s |
Unit tests for the |
|
|
✅ pass |
0.01s |
The |
|
|
✅ pass |
0.03s |
ADR-0060 §2 — the thread-safe pool |
|
|
✅ pass |
0.00s |
Path parsing / validation (docs/reference/03-addressing.md). |
|
|
✅ pass |
0.00s |
The RFC-0027 path-label value, its §5.3 ELEMENT, and the mint table — codec, element grammar, the §12.5 vectors, mint, lookup, retire, SATURATE-AND-RETIRE, and §8.3. |
|
|
✅ pass |
0.00s |
RFC-0027 car 3 — the mixed-element codec ( |
|
|
✅ pass |
0.00s |
The two links, spelled as the RFC-0014 mount runs a real node uses. |
|
|
✅ pass |
0.00s |
The origin’s own first hop — the one hop no peer ever sees (§4.1). |
|
|
✅ pass |
0.00s |
The inbound link, spelled as the three-segment mount run a real node uses. |
|
|
✅ pass |
0.00s |
PATH_REF (0x14) codec test — the bound-path wire form of RFC-0024 §4. |
|
|
✅ pass |
0.00s |
rope_t small-buffer storage + the value-consumption accessors (ADR-0053 §6). |
|
|
✅ pass |
0.00s |
|
|
|
✅ pass |
0.00s |
The cursor window guarantee in a RELEASE build (#986) — the gate that cannot pass vacuously under |
|
|
✅ pass |
0.01s |
L0/L1 substrate tests: refcount lifetime (the canonical intrusive_ptr orderings), zero- copy subview/concat, rope serialization equivalence (the docs/reference/02 proof obligation), the view->TLV cast claim with the lifetime gap M1 left open now closed, and the bounded pool backend. |
Graph (L4)¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
Per-endpoint :acl — storage (#81-A) + core-subset enforcement (#81, ADR-0018/ 0020/0026). |
|
|
✅ pass |
0.09s |
ACL-cache coherence under a concurrent subtree invalidation (#880, ADR-0078). |
|
|
✅ pass |
0.00s |
#1665 — an attributed op reads the ACE-expiry clock only when an ACL is evaluated. |
|
|
✅ pass |
0.01s |
— |
— |
|
✅ pass |
0.03s |
RFC-0010 owner app fields: the field descriptor table, |
|
|
✅ pass |
0.00s |
#82 — in-band vertex creation via a |
|
|
✅ pass |
0.00s |
Per-cause delivery-drop counters ( |
|
|
✅ pass |
0.00s |
RFC-0009 §D extended to peer departure — subscriber-edge eviction on link teardown, and edge-slot reuse. |
|
|
✅ pass |
0.15s |
effective_acl_t unit test (ADR-0050, the previously-untested half) — the pure effective- ACL merge semantics driven directly with synthetic ACE lists (no graph, no locks, no wall clock): own-before-ancestors ordering, nearest-first ancestor order, INHERIT gating at merge time, any-present-ACE-closes (even expired), open-by-default over an empty merge, and DENY first-match-per-bit ordering under the full policy. |
|
|
✅ pass |
0.00s |
L4 fold, Slice 0 — the folded |
|
|
✅ pass |
0.19s |
L4 graph-runtime tests. |
|
|
✅ pass |
19.14s |
#1049 — |
|
|
✅ pass |
0.00s |
#477 — the store/delivery path’s nothrow soft-fail discipline under OOM. |
|
|
✅ pass |
0.00s |
#361 §5 / ADR-0039 §1 — the per-write LKV allocation seam on |
|
|
✅ pass |
0.37s |
#1778 — every growth site of the graph core, driven to exhaustion of its table source. |
|
|
✅ pass |
0.00s |
ADR-0060 — the write-path value byte-buffer seam on |
|
|
✅ pass |
0.00s |
#406 / RFC-0011 — the node identity facet: |
|
|
✅ pass |
0.00s |
Registry teardown — |
|
|
✅ pass |
6.45s |
graph_t::retire() — RFC-0009 §B/§C/§E.6 vertex retirement (#407). |
|
|
✅ pass |
0.00s |
security_acl unit test (ADR-0050) — drives the PURE ACL policy seam directly, no graph, no locks, no wall clock: both adapters (allow_only / full), the ACE edge cases (expiry, EVERYONE@, per-bit matching, INHERIT-flag filtering, first-match-per-bit DENY ordering), and the typed parse/build round-trip that replaces the per-test byte builders. |
|
|
✅ pass |
0.00s |
RFC-0005 — subtree subscriptions (vertical bubbling), branch-write decomposition, and write-creates. |
|
|
✅ pass |
0.00s |
RFC-0005 §C follow-on — the COMPOSED BRANCH READ: a plain READ of a vertex with ≥ 1 registered child serves the folded POINT tree of its registered subtree’s landed LKVs. |
|
|
✅ pass |
0.04s |
vertex_t verb-interface unit tests — a BARE vertex, no graph_t (the point of the verb seam: the vertex’s storage/readiness/edge/ACL state is testable in isolation). |
|
|
✅ pass |
0.00s |
The vertex RAM-diet regression gate (#361 §8): compile-time ceilings on |
Net (FWD plane)¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
ADR-0062 increment 2 — a warm binding is fast, and it invalidates correctly. |
|
|
✅ pass |
0.10s |
ADR-0084: a remote AWAIT is answered later, from a one-shot receiver-side waiter, and never holds the receive context of the link it arrived on. |
|
|
✅ pass |
0.00s |
#833 — a REFUSED forwarding bind must strand neither the out-label it took nor the egress route retained with it, through the production |
|
|
✅ pass |
0.49s |
RFC-0004 / ADR-0035 slice 4 — the route-handle: ws delivery-compaction, proven over LIVE transport_ws. |
|
|
✅ pass |
0.00s |
#974 — a label-compacted (COMPACT) delivery is ACL-gated under the INBOUND LINK’s name, exactly like the full-route |
|
|
✅ pass |
0.00s |
RFC-0004 / ADR-0035 slice 4 (#136) — the PRODUCER remote fan-out. |
|
|
✅ pass |
0.00s |
#730 — every rope flatten |
|
|
✅ pass |
0.00s |
fwd_frame_view unit test — drives the FWD offset-dispatch cluster directly (no router, no transports), the point of extracting it from fwd_router.cpp (the length_prefix_framer precedent): first-dst-seg / op / control peeks over BOTH cursors (contiguous span + adversarially split rope), the shrunk-dst / grown-src head rebuild proved BYTE-EXACT against a reference re-encode, stack_writer clamp-to-empty overflow, and malformed rejects. |
|
|
✅ pass |
0.00s |
#1648 review — the router’s two in-place ingress reads (the |
|
|
✅ pass |
0.00s |
The malformed-control-frame rejection surface of |
|
|
✅ pass |
0.30s |
RFC-0004 / ADR-0035 slice 3 — multi-hop FWD forwarding + zero-copy |
|
|
✅ pass |
0.00s |
#1645 — a node originates a forwarded READ, WRITE or append through |
|
|
✅ pass |
0.00s |
#913 — a re-advertise cycle must burn no downstream label and leak no egress entry. |
|
|
✅ pass |
0.00s |
RFC-0004 §E.1 — a MID-CHAIN reconnect self-heals: |
|
|
✅ pass |
0.00s |
ADR-0053 ④b — the FWD forward hop over a MULTI-LINK rope, WITHOUT flattening. |
|
|
✅ pass |
0.07s |
#914 — a router sink’s |
|
|
✅ pass |
0.00s |
#1612 — a request the terminus cannot serve for want of MEMORY is answered with an addressed |
|
|
✅ pass |
0.00s |
The terminus resolver’s malformed- |
|
|
✅ pass |
0.00s |
#1709 — a terminus reply leaves through the link the request arrived on, with no by-name lookup, whenever that link is point-to-point. |
|
|
✅ pass |
0.00s |
The TWO-MOUNT route (#419): a |
|
|
✅ pass |
0.00s |
The per-module mount-routing primitives (ADR-0061 / RFC-0014 S2a). |
|
|
✅ pass |
0.09s |
ADR-0063 §3 — control-plane writers are serialized, and the forward reader is not. |
|
|
✅ pass |
0.01s |
RFC-0004 / ADR-0035 — op_resolver_t host tests, over the ADR-0041 terminus arena. |
|
|
✅ pass |
0.00s |
ADR-0053 §7 (3c-ii) — the DIFFERENTIAL ORACLE for the two terminus-resolver instantiations. |
|
|
✅ pass |
0.06s |
route_handle_t unit test (Brick 4, ADR-0038 §3 / ADR-0039): the label state is per- connection — pmr-backed tables with a per-link mutex. |
|
|
✅ pass |
1.87s |
#83 Stage-1 — transport/connection as a |
Transport¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.02s |
#383 — can_tx_pool_t ownership/backpressure host suite. |
|
|
✅ pass |
4.40s |
M6 TCP transport tests: length-prefix framing over a real localhost TCP stream. |
|
|
✅ pass |
1.74s |
#55 (increment 2) — can_transport_t SocketCAN-binding tests over an in-memory fake link, so they pass in plain Docker with NO kernel CAN (vcan). |
|
|
✅ pass |
0.34s |
ADR-0044 — stateless transport-peer enumeration + transparent per-peer FWD over the CAN bus binding, proven over the in-memory fake link (no kernel CAN): |
|
|
✅ pass |
0.00s |
#55 (increment 2) — REAL-bus smoke test for can_transport_t over Linux SocketCAN. |
|
|
✅ pass |
0.56s |
Transport seam-conformance suite. |
|
|
✅ pass |
1.47s |
M5 UDP transport tests: raw frame delivery over a real localhost UDP socket, and an end- to-end two-node FWD delivery through graph_t + fwd_router_t over UDP (the explicit-source- routed net plane, ADR-0040 — no bridge_t/ROUTER). |
|
|
✅ pass |
0.10s |
#903 — the full-write helpers must RESUME an interrupted write, not truncate. |
|
|
✅ pass |
2.78s |
#54 — transport_ws SERVER socket-layer tests. |
Examples¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.07s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.05s |
In-process publish/subscribe over the L4 graph — the M3 P0 node, end to end. |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.20s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.40s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.21s |
— |
— |
|
✅ pass |
0.20s |
— |
— |
|
✅ pass |
0.01s |
Pub/sub fan-out — one publisher, a growing set of subscribers, and the per-delivery dispatch cost as fan-out scales. |
|
|
✅ pass |
0.00s |
L1 scatter-gather — compose a multi-link |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
The three composition axes, made visible — why a libtracer node is a tree of ropes, not a rope of ropes. |
|
|
✅ pass |
0.01s |
Two nodes over a wire — an FWD write routed between two graphs, and the end-to-end delivery latency across the “wire”. |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.02s |
Wire codec deep-dive — build a structured frame, inspect its bytes, and measure encode / decode / round-trip throughput. |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
L2/L3 wire codec round-trip — build a TLV, encode to bytes, decode back. |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
other¶
suite |
result |
time |
covers |
source |
|---|---|---|---|---|
|
✅ pass |
0.00s |
The admission context’s LINK claim (#1650): |
|
|
✅ pass |
0.00s |
The pre-store ADMISSION seam: |
|
|
✅ pass |
0.00s |
The BATCH record ( |
|
|
✅ pass |
0.00s |
#1468 — |
|
|
✅ pass |
4.00s |
RFC-0024 car 3 — the bound-path FORWARDER hop and the origin-side bind, end to end. |
|
|
✅ pass |
0.00s |
RFC-0024 — bound-path routing and minting, at the terminus. |
|
|
✅ pass |
2.78s |
— |
— |
|
✅ pass |
0.20s |
The ADR-0044 BUS module as a build-time-closed seam (#375 deliverable 3) — what |
|
|
✅ pass |
0.00s |
Receiver-ctx churn (#884): a re-added NAME resolves to its CURRENT tenancy, and remove/re-add cycles do not grow the router’s published receiver chain. |
|
|
✅ pass |
0.00s |
graph_t::collect() / parked_seam_count() — the explicit end of retirement’s value-seam park (#576, the direction-3 ruling that supersedes ADR-0072). |
|
|
✅ pass |
0.00s |
#1810 — a CI leg runs the configuration its name says: the bound LKV slot, reclamation policy and ACL policy are printed, and checked against the leg’s expectation. |
|
|
✅ pass |
0.00s |
#927 / #985 — |
|
|
✅ pass |
0.00s |
|
|
|
✅ pass |
0.00s |
Unit tests for the core container set (#1776, ADR-0083 Decision 2 and 9): the vector ( |
|
|
✅ pass |
0.00s |
RFC-0025 §4.1 delivery classes, HONOURED — what a class actually selects once Amendments 2, 3 and 4 have moved the machinery (#1204 phase 3). |
|
|
✅ pass |
0.04s |
|
|
|
✅ pass |
0.00s |
#1442 / #1448 — NOBODY deep-copies a subscription’s cold half any more. A republish shares it (so an admission’s allocation count is flat in the edges already on the vertex) and so does the dispatch snapshot (so a WRITE’s allocation count is flat in the remote fan-out). |
|
|
✅ pass |
0.10s |
The published edge array and its edge pin (#635): a snapshot sees the OLD edge set or the NEW one and never a torn mixture, an unsubscribe stops delivering at once, the pin is never held across a dispatch, and nothing is freed under a reader or leaked at teardown. |
|
|
✅ pass |
0.00s |
RFC-0004 Amendment 2 (#1502, ruling on #1491) — a zero-length |
|
|
✅ pass |
0.00s |
Unit tests for the RFC-0002 protocol error registry (error.hpp). |
|
|
✅ pass |
4.00s |
— |
— |
|
✅ pass |
4.00s |
— |
— |
|
✅ pass |
8.71s |
— |
— |
|
✅ pass |
2.47s |
— |
— |
|
✅ pass |
9.10s |
— |
— |
|
✅ pass |
4.00s |
— |
— |
|
✅ pass |
0.00s |
#1719 — the test-only fault-injection hooks are |
|
|
✅ pass |
0.00s |
The field surface’s READ/WRITE dispatch parity guards (#869). |
|
|
✅ pass |
0.00s |
#831 — BOTH folded READs’ POINT headers draw from |
|
|
✅ pass |
0.01s |
The fused guarded publish (#1715): on the guarded write-sequence binding, a publish opens ONE guard section for the LKV swap and the sequence bump together. |
|
|
✅ pass |
0.00s |
Unit tests for the grammar’s total-encoded-size bound (grammar.hpp, #921). |
|
|
✅ pass |
0.00s |
The one-release alias window of #1703: every pre-move spelling of the guard vocabulary still names the layer-neutral type it moved to. |
|
|
✅ pass |
2.88s |
— |
— |
|
✅ pass |
0.01s |
The host guard sized by the target (#1716): stripe alignment follows |
|
|
✅ pass |
0.00s |
#1505 — a HANDLER write allocates ONE block fewer per write than a retaining write, at EVERY link count. The non-retaining role is never the more expensive one. |
|
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
2.65s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.01s |
— |
— |
|
✅ pass |
7.65s |
— |
— |
|
✅ pass |
1.02s |
— |
— |
|
✅ pass |
0.18s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.42s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
2.12s |
— |
— |
|
✅ pass |
0.00s |
— |
— |
|
✅ pass |
1.03s |
— |
— |
|
✅ pass |
0.00s |
|
|
|
✅ pass |
0.00s |
|
|
|
✅ pass |
0.00s |
Unit tests for the heap-free stored callable (inline_fn.hpp, #1671). |
|
|
✅ pass |
0.35s |
— |
— |
|
✅ pass |
0.35s |
— |
— |
|
✅ pass |
0.00s |
#1664 — |
|
|
✅ pass |
0.00s |
#1670 — the two LINK MODULES are lean by default: |
|
|
✅ pass |
0.41s |
RFC-0014 §4 S5 (#492) — the link-liveness ENGINE drives |
|
|
✅ pass |
0.00s |
#1266 / #1417 — the CARRIED link token, and the four things about it that have to be BUILT and SHOWN rather than asserted. |
|
|
✅ pass |
0.02s |
ADR-0069, RFC 0028 §5.5 — the LKV slot policies, both of them, in whatever build this is. |
|
|
✅ pass |
0.00s |
#1618 — no LKV slot policy may livelock a higher-priority reader against a lower-priority writer on one CPU. |
|
|
✅ pass |
0.01s |
— |
— |
|
✅ pass |
0.00s |
|
|
|
✅ pass |
0.03s |
#882 — a shape-flipping rebind must never let a forward route a BUS link point-to-point. |
|
|
✅ pass |
0.00s |
The mount WIDTH lift: a mount of any width registers, resolves, and resolves the SAME way on the FWD plane and the COMPACT plane (#523, #765). |
|
|
✅ pass |
0.20s |
RFC-0014 S6 (#492) — the control-plane lock-order invariant: |
|
|
✅ pass |
2.88s |
— |
— |
|
✅ pass |
0.01s |
RFC-0008 Amendment 2 (#1506) — the non-retaining-vertex contract, plus the HANDLER read seam (RFC-0028 D11). |
|
|
✅ pass |
0.00s |
RFC-0028 slice 7 — one callback idiom (D10), one read type (D11), and a HANDLER target that adopts the published value like a stored target. |
|
|
✅ pass |
0.70s |
#491 / ADR-0073 Consequences — third-party orchestration end-to-end: an orchestrator C wires a flow between two OTHER nodes (B producer → A consumer), then departs; delivery must continue after the departure. |
|
|
✅ pass |
0.00s |
RFC-0014 Amendment 2 (§5.1) — a handler vertex declares a payload-type → required- ACL-right table, and the ONE write gate demands what it says (#492 S2c). |
|
|
✅ pass |
0.21s |
#1294 — the peer-receiver seam carries an opaque per-peer HANDLE, not a name string. |
|
|
✅ pass |
0.01s |
#1712 — the per-vertex pending-mark hint: an eager write to an UNMARKED vertex pays no key render, no allocation and no graph-wide sweep lock, however many other vertices hold an |
|
|
✅ pass |
2.88s |
— |
— |
|
✅ pass |
0.03s |
The bytes each backend actually asks for, either side of every size-class boundary (#1768, #1775, #1777). |
|
|
✅ pass |
0.00s |
#1460 phase (b) — RFC-0025 conformance vector 12 |
|
|
✅ pass |
0.00s |
#1546 — the reference PLAYOUT helper ( |
|
|
✅ pass |
0.00s |
The SINGLE-MEMBER ( |
|
|
✅ pass |
0.00s |
RFC-0025 §4.1.2 (Amendment 3, clause 5) — |
|
|
✅ pass |
0.00s |
RFC-0022 (as amended): delivery policy is per-subscription; |
|
|
✅ pass |
0.00s |
#1583 — every #873 phase-3 READ-BACK ENCODER draws its owned segment from |
|
|
✅ pass |
0.06s |
The leaf/branch fork of |
|
|
✅ pass |
0.00s |
The ADR-0080 reclamation seam — WHEN a retired subscription’s |
|
|
✅ pass |
0.00s |
#684 — a rebind of a LIVE name must not touch the published mount encoding. |
|
|
✅ pass |
0.62s |
RFC-0028 §6.9 / §8.2 (#1620): the retained send. A queued link keeps the value (one reference) and copies only the frame’s head. |
|
|
✅ pass |
0.00s |
The SUBSCRIPTION-RETAINED seam (#1610): the two allocations a remote SUBSCRIBE keeps for the life of the subscription can be taken from a backend of the host’s choosing. |
|
|
✅ pass |
0.00s |
RFC-0028 slice 6 (D4) — retention is ONE per-vertex, per-field policy: |
|
|
✅ pass |
0.00s |
#1460 phases (a) and (c) — RFC-0025 conformance vector 12 |
|
|
✅ pass |
0.00s |
#1503 step 3 — |
|
|
✅ pass |
0.00s |
#1582 — the router’s peer-reachable |
|
|
✅ pass |
0.00s |
RFC-0028 §6.9 (#1626): the ingress loan. A receive block carries a value-header reserve, and the value stored from that block is placed IN the reserve. |
|
|
✅ pass |
11.57s |
#838 — a host stream send into a stalled peer is BOUNDED, counted, and the peer that keeps stalling is closed rather than blocked on forever. |
|
|
✅ pass |
0.20s |
#1223 step 2 — an ACCEPTED |
|
|
✅ pass |
2.88s |
— |
— |
|
✅ pass |
0.03s |
The size-classed slab pool and the host default root (#1777, ADR-0083 Decision 6). |
|
|
✅ pass |
1.96s |
— |
— |
|
✅ pass |
5.77s |
— |
— |
|
✅ pass |
0.00s |
#1503 step 5 / RFC-0010 Amendment 1 — the node-scoped seam census: |
|
|
✅ pass |
0.00s |
RFC-0010 Amendment 2 (#1503 residual) — the NET-PLANE |
|
|
✅ pass |
0.00s |
#1713 — a STREAM write takes its vertex stripe lock ONCE and makes NO heap allocation in the common case: one locked admit-and-take into a stack-first buffer. |
|
|
✅ pass |
0.00s |
#739 — |
|
|
✅ pass |
0.00s |
Target adopt — a subscription’s target leg takes a reference on the published block instead of minting one of its own (RFC-0028 slice 4, D2; the fan-out half of #1620). |
|
|
✅ pass |
0.00s |
The #830 ablation: |
|
|
✅ pass |
0.00s |
#795 — the terminus FWD{REPLY}’s egress-construction segments (the reply HEAD and, on a mint, the trailing |
|
|
✅ pass |
0.00s |
#766 — the TERMINUS resolver’s rope-tier flattens draw from the router’s injected |
|
|
✅ pass |
0.19s |
The shared test runner, under test by itself (#874). |
|
|
✅ pass |
0.00s |
#1532 — |
|
|
✅ pass |
6.05s |
#848 — the transport EGRESS framing path never aborts on a tight heap: a refusing allocator must produce a DROPPED FRAME AND A LIVE NODE, never |
|
|
✅ pass |
0.37s |
— |
— |
|
✅ pass |
0.03s |
The nothrow |
|
|
✅ pass |
0.00s |
#981/#1570 — the |
|
|
✅ pass |
0.41s |
— |
— |
|
✅ pass |
0.71s |
— |
— |
|
✅ pass |
0.00s |
|
|
|
✅ pass |
2.89s |
— |
— |
|
✅ pass |
0.00s |
#375 — a HANDLER’s |
|
|
✅ pass |
0.00s |
#948 — a malformed |
|
|
✅ pass |
0.07s |
The 32-bit write sequence (#1621, RFC-0028 D6): its width, the wrap, and |
|
|
✅ pass |
0.07s |
The 32-bit write sequence (#1621, RFC-0028 D6): its width, the wrap, and |
Warning
No source could be resolved from the CMake build graph for: acl_full_removed, bus_can_guard, esp_ws_client_dial, esp_ws_client_dial_stats, esp_ws_client_liveness, esp_ws_client_recv, esp_ws_client_teardown, esp_ws_client_traffic_stats, example_acl_everyone_reserved, example_acl_expiry, example_acl_inherit, example_acl_open_by_default, example_acl_parse_strict, example_acl_policy_profiles, example_acl_right_bits, example_acl_subject_resolver, example_graph_await, example_graph_children, example_graph_handler_vertex, example_graph_read_write, example_graph_register, example_graph_retire, example_graph_stream, example_graph_write_creates, example_mem_block_array, example_mem_block_source, example_mem_bump_source, example_mem_bump_upstream, example_mem_pool_source, example_mem_size_classes, example_mem_source_resource, example_mem_source_vs_backend, example_net_can_bus_peers, example_net_dial_and_listen, example_net_kind_catalog, example_net_multi_peer_listener, example_net_tcp_stream_framing, example_net_transport_seam, example_net_udp_datagram, example_net_ws_upgrade, example_route_child_table, example_route_dst_is_source_route, example_route_label_compact, example_route_label_stale, example_route_multi_hop, example_route_qualified_mount, example_route_reply_home, example_route_terminus_or_forward, example_sub_callback, example_sub_durability_latch, example_sub_retire, example_sub_subtree, example_sub_terminal_delivery, example_sub_unsubscribe, example_sub_unsubscribe_from_dispatch, example_view_borrow, example_view_device_rope, example_view_pool_backend, example_view_rope_compose, example_view_rope_subrope, example_view_segment_refcount, example_view_subview, example_view_sync_pool, example_wire_arena_decode, example_wire_decode_refusals, example_wire_lazy_view, example_wire_packed_path, example_wire_path_escape, example_wire_structured_vs_opaque, example_wire_tlv_header, example_wire_trailer, guard_rename, httpd_ws_admission, httpd_ws_adopted_host, httpd_ws_alloc_softfail, httpd_ws_auth, httpd_ws_close_peer, httpd_ws_counters, httpd_ws_counters_traffic_stats, httpd_ws_departure_cost, httpd_ws_drain_budget, httpd_ws_drain_budget_unhooked, httpd_ws_eviction_lock, httpd_ws_fanout_alloc, httpd_ws_fanout_wait, httpd_ws_fanout_width, httpd_ws_in_call_reply, httpd_ws_keepalive, httpd_ws_rx_owned, httpd_ws_send_stall, httpd_ws_session_identity, httpd_ws_teardown, httpd_ws_tx_large_class, httpd_ws_tx_pool, inline_fn_reject_OVERSIZE, inline_fn_reject_OWNING, lkv_slot_removed, no_atomic_removed, pin_instrument_removed, single_writer_removed, spin_pool_guard, spin_slot_guard, transport_include_guard, twai_backpressure, twai_rx_ingress, weakly_ordered_removed. Those rows fall back to a hand-written description, which is exactly the drift this resolution exists to remove.
How every suite is verified¶
Beyond this Release pass, the same suites run under three more configurations in CI (core-ci.yml), and the net forward path carries an absolute allocation gate:
configuration |
what it proves |
|---|---|
Release (this page) |
functional correctness, byte-exact wire behavior |
ASan + UBSan |
no leaks, no undefined behavior, no buffer overruns |
TSan |
the lock-free LKV + concurrent forward paths are race-free |
GCC-13 + GCC-15 |
the toolchain floor + the ESP on-silicon compiler |
16KB zero-heap gate |
the FWD forward hop allocates 0 bytes ( |
Cross-implementation conformance (C++ / TypeScript / Rust agree on every vector) and the live latency/throughput numbers are on the Performance page.