open-standards/eoc/eoc-rs/crates/eoc
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 3513b9cc5d
Some checks failed
standards workspaces build + test / jouleclaw-rs (pull_request) Has been cancelled
standards workspaces build + test / aac-rs (pull_request) Has been cancelled
standards workspaces build + test / arl-rs (pull_request) Has been cancelled
standards workspaces build + test / eoc-rs (pull_request) Has been cancelled
standards workspaces build + test / jcp-rs (pull_request) Has been cancelled
standards workspaces build + test / joule-code-rs (pull_request) Has been cancelled
standards workspaces build + test / joule-ui-rs (pull_request) Has been cancelled
standards workspaces build + test / joulecontract-rs (pull_request) Has been cancelled
standards workspaces build + test / jouledesk-rs (pull_request) Has been cancelled
standards workspaces build + test / joulehook-rs (pull_request) Has been cancelled
standards workspaces build + test / map-rs (pull_request) Has been cancelled
standards workspaces build + test / mesh-rs (pull_request) Has been cancelled
standards workspaces build + test / openpay (pull_request) Has been cancelled
standards workspaces build + test / proof-rs (pull_request) Has been cancelled
standards workspaces build + test / sandbox-rs (pull_request) Has been cancelled
standards workspaces build + test / sense-rs (pull_request) Has been cancelled
standards workspaces build + test / smart-byte-rs (pull_request) Has been cancelled
standards workspaces build + test / macOS energy backend (jcp-energy) (pull_request) Has been cancelled
eoc: the in-process burn test's backend is built only on macOS, where its one test runs
`BurningUnestimatedBackend` exists for one test,
`in_process_work_is_measured_by_the_process_counter`, which is
`#[cfg(target_os = "macos")]`: it asserts this process's own counter is live,
and `process_energy_status()` is always `Unavailable` off macOS, where
`detect_in_process()` is `detect()`. The backend itself had no cfg, so on every
other target it was never constructed, and `cargo clippy --all-targets` for
x86_64-unknown-linux-gnu warned "struct `BurningUnestimatedBackend` is never
constructed". On macOS there was no warning, since the test builds it there.

No test off macOS was meant to use it. A backend that claims an estimated zero
for real work, on a host with no live counter, costs that zero under
eoc-cascade's rule (with no live span the stage's own figure stands); a test
there would pin a 0 for work that ran, not a measurement. The non-macOS path
of the CLI's cascade is already covered by
`work_on_an_unmetered_host_keeps_its_estimate`, with a backend that does
estimate. So the struct and its impl take the test's cfg instead of being
used somewhere they would assert the wrong thing.

clippy on `eoc` with `--all-targets`, for aarch64-apple-darwin and for
x86_64-unknown-linux-gnu: no warnings in the crate (the second had the one
above before this).
On an M5 Max (macOS 27.0.1) the test still builds it and passes: "eoc
in-process cost: 260170 µJ (measured)". The eoc workspace, rebased onto the
eoc-agent changes below it: 705 passed, 0 failed, 3 ignored; eoc-meter's
tests/process_energy.rs: 4 passed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-30 22:41:13 -04:00
..
src eoc: the in-process burn test's backend is built only on macOS, where its one test runs 2026-09-30 22:41:13 -04:00
Cargo.toml eoc-meter: CPU-rail liveness pairs consecutive samples, and every step of it is tested 2026-09-30 08:04:39 -04:00