Transaction Science
4d745abf6b
energy meters on real hardware / RAPL and NVML on jetson-hub (pull_request) Successful in 44s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 20s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 1m47s
standards workspaces build + test / macOS energy backends (pull_request) Failing after 2m42s
standards workspaces build + test / eoc-rs (eoc/eoc-rs, -p eoc-meter --features cuda, eoc-rs, linux) (pull_request) Successful in 2m17s
eoc-meter: say where the sampler-re-reads property is actually pinned ...
The GPU-freshness report left a comment explaining why a rise the oracle saw is
not one the probe must have seen. It did not say what still covers the property
that assertion was reaching for, so the obvious next reader restores a hardware
assertion and reintroduces the flake.
It is covered deterministically, per sample, by the scripted probes:
`probe_with_a_single_batch_jump_is_frozen` drives `GPU Energy` to a different
value at every sample and asserts each one is exactly what the rule was handed,
and `probe_with_one_die_live_and_one_frozen_is_frozen` does the same. A sampler
that cached one reading fails those on sample 1, on every host, with no
dependence on what the hardware happens to do.
So the earlier claim that the report gave up that coverage was wrong: it gave up
nothing, and driving GPU work inside the probe's window to restore a hardware
assertion is unnecessary. The comment now says so, and says why no sound
hardware witness exists on the CI host anyway -- its CPU rails are frozen and
its GPU rail is activity-driven.
Comment only; no behaviour change.
Co-Authored-By: Claude Opus 5 <[email protected] >
2026-10-15 01:06:15 -04:00
eoc: a hit prints its estimate and the calibration it came from
2026-10-13 02:22:58 -04:00
eoc-agent: a local model's measured step is a measured span
2026-10-01 01:27:42 -04:00
eoc docs: what a resolve is charged, with the measured figures; the example prints the unmetered baseline
2026-10-13 02:22:58 -04:00
eoc-carbon: an account and an SCI score are measured only where every part was, and a run with no correct answer has no score
2026-09-30 21:07:25 -04:00
eoc docs: what a resolve is charged, with the measured figures; the example prints the unmetered baseline
2026-10-13 02:22:58 -04:00
eoc docs: what a resolve is charged, with the measured figures; the example prints the unmetered baseline
2026-10-13 02:22:58 -04:00
ingest wave A4: 3 crates · smart-byte-atproto + op-openbanking + eoc-distributed
2026-05-24 12:22:09 -04:00
Repo-wide toolchain refresh + jouleclaw policy/sandbox updates
2026-06-07 17:04:45 -04:00
eoc-carbon: an SCI score is only as measured as the joules it was computed from
2026-09-30 20:17:24 -04:00
Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc
2026-05-23 13:24:05 -04:00
Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc
2026-05-23 13:24:05 -04:00
eoc: the CLI's cascade is metered by this process's own counter, because all of its stages run in-process
2026-09-30 22:39:01 -04:00
ingest wave F: 3 crates · op-crypto-extra + smart-byte-acdc + eoc-memory
2026-05-24 17:28:24 -04:00
eoc-meter: say where the sampler-re-reads property is actually pinned
2026-10-15 01:06:15 -04:00
Repo-wide toolchain refresh + jouleclaw policy/sandbox updates
2026-06-07 17:04:45 -04:00
Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc
2026-05-23 13:24:05 -04:00
ingest wave C: 3 crates · op-statements + smart-byte-activitypub + eoc-observability
2026-05-24 13:51:09 -04:00
ingest wave D: 3 crates · op-fraud-graph + smart-byte-ilp + eoc-quantize
2026-05-24 16:10:10 -04:00
ingest wave A3: 3 crates · op-ewallets-asia + smart-byte-zk + eoc-rag
2026-05-24 12:08:49 -04:00
Repo-wide toolchain refresh + jouleclaw policy/sandbox updates
2026-06-07 17:04:45 -04:00
eoc-route-learned: unbreak the build — rand_distr 0.4 pulled rand 0.8
2026-07-20 12:46:50 -04:00
ingest wave E: 3 crates · op-bin + smart-byte-tendermint + eoc-safety
2026-05-24 16:52:07 -04:00
Repo-wide toolchain refresh + jouleclaw policy/sandbox updates
2026-06-07 17:04:45 -04:00
eoc-streaming: a stream nothing metered has no energy figure, never 0 µJ
2026-09-30 20:17:36 -04:00
eoc: pin rand off 0.10.2, which does not compile
2026-08-27 13:32:56 -04:00
Repo-wide toolchain refresh + jouleclaw policy/sandbox updates
2026-06-07 17:04:45 -04:00
Parallel ingest: 9 issues' worth of work across openpay / smart-byte / eoc
2026-05-23 13:24:05 -04:00
4d745abf6b