| Filename | Latest commit message | Latest commit date |
|---|---|---|
3e5a9cec26
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 8s
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m8s
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m21s
standards workspaces build + test / proof-rs (proof/conformance/v1/joulespec.toml, proof-conformance, proof/proof-rs, proof-rs, linux, true) (pull_request) Successful in 1m23s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 1m38s
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, -p sandbox-tee --features amd-kds,intel-pcs, sandbox-rs, linux) (pull_request) Successful in 5m1s
energy meters on real hardware / sink decode table · per-task energy and the GPU rail on macOS (pull_request) Successful in 2m56s
standards workspaces build + test / joulecontract-rs (joulecontract/joulecontract-rs, joulecontract-rs, linux-arm64, true) (pull_request) Successful in 5m1s
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 4m44s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 6m47s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 16m21s
energy meters on real hardware / RAPL and NVML on jetson-hub (pull_request) Successful in 36s
energy meters on real hardware / sink decode table · RAPL on jetson-hub (NVML surveyed) (pull_request) Successful in 2m21s
On a multi-die Intel package the kernel scopes RAPL per die and lists one top-level intel-rapl:<n> zone per die, named "package-<p>-die-<d>" (intel_rapl_common's "package-%d-die-%d", used when the MSRs are not package scope and a package has more than one die). The probe accepted only "package-<n>", so such a host listed no package zone: estimated, or, with the MSR fallback, read through the MSRs as root only. A zone's name now names a package's domain when it is "package-<digits>" or "package-<digits>-die-<digits>", and nothing looser (not psys, dram, "package-", "package-0-die-", "package-0-core-0", "package-0-die-1-die-2"), so every die's zone is summed into the CPU figure under the same rules: every domain readable and live, or no figure. The hardware tests' oracles (the powercap one, and the MSR one's check for a powercap package) apply the same name rule. Tests: the name rule over both forms and the near misses; a fake two-die powercap tree (two die zones, psys, each die's core subzone) holding exactly the two die zones, metering a span as their rise alone, and frozen when one die holds. Pass on Linux x86_64 (cargo test -p sandbox-meter; clippy clean apart from the existing type_complexity errors in tests/nvml_hardware.rs) and in the macOS CI step (both greps; clippy on sandbox-meter and sandbox-proof clean). Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| sandbox-attest | ||
| sandbox-build | ||
| sandbox-capability | ||
| sandbox-cli | ||
| sandbox-conformance | ||
| sandbox-exec-microvm | ||
| sandbox-exec-os | ||
| sandbox-exec-wasm | ||
| sandbox-jcp | ||
| sandbox-mcp | ||
| sandbox-meter | ||
| sandbox-proof | ||
| sandbox-proof-wasm | ||
| sandbox-runtime | ||
| sandbox-schema | ||
| sandbox-tee | ||