Transaction Science
208ffd374f
energy meters on real hardware / sink decode table · per-task energy and the GPU rail on macOS (push) Successful in 5m13s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
energy meters on real hardware / RAPL and NVML on jetson-hub (push) Failing after 2m37s
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (push) Failing after 15m17s
energy meters on real hardware / sink decode table · RAPL on jetson-hub (NVML surveyed) (push) Failing after 20s
The public IOReport status variants say what they mean under the 3-tick cap ...
The docs of each crate's IoReportStatus still stated the liveness rule as it stood
before the cap: five advances, four in five of the intervals observed, 300 ms of
wall time. Live, and Frozen where it states the rule, now say it as the spec texts
do: what an interval is, that only one no longer than three of the probe's ticks
(75 ms at its 25 ms tick) counts, that a longer one counts as nothing, and that the
300 ms is the summed length of the intervals that count. Frozen also says that a
probe the host held, so that too few of its intervals counted, reads Frozen. In
eoc-meter, jcp-energy, jouleclaw-energy, proof-cascade and sandbox-meter. Doc
comments only.
Changelog: none
Co-Authored-By: Claude Opus 5.5 <[email protected] >
2026-11-07 08:30:52 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
sandbox: RAPL read through the MSRs is attested as RAPL, and the hardware tests' oracles read the MSRs where powercap lists no package
2026-11-05 10:23:03 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp: a ModelIn caveat says which model a grant authorizes, and the frame names the model it runs
2026-10-17 04:21:21 -04:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
The public IOReport status variants say what they mean under the 3-tick cap
2026-11-07 08:30:52 -05:00
sandbox: RAPL read through the MSRs is attested as RAPL, and the hardware tests' oracles read the MSRs where powercap lists no package
2026-11-05 10:23:03 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
sandbox: RAPL read through the MSRs is attested as RAPL, and the hardware tests' oracles read the MSRs where powercap lists no package
2026-11-05 10:23:03 -05:00
208ffd374f