| Filename | Latest commit message | Latest commit date |
|---|---|---|
d698f47278
Some checks failed
joule-code conformance gate / joule-moq-relay, its own energy on a counter (macos) (push) Successful in 52s
joule-code conformance gate / Build + round-trip C1-C4 vectors (push) Successful in 1m38s
joule-code conformance gate / joule-moq-relay, every target (push) Successful in 3m7s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Failing after 4m22s
wai release binaries build on Windows / the seven release binaries · windows (push) Successful in 14m14s
joule-code conformance gate / joule-moq-ingest, every target (push) Successful in 21m40s
joule-moq-room room service / joule-moq-room · does this change touch it (push) Has been cancelled
joule-moq-room room service / joule-moq-room, every target (push) Has been cancelled
cpu_us() declared POSIX getrusage for every target, so linking wai-ingest for x86_64-pc-windows-msvc failed (LNK2019, unresolved external symbol getrusage) and wai-v0.5.0's Windows leg produced no archive. It is now getrusage on unix, GetProcessTimes (kernel32) on Windows, and zero where a platform gives no process CPU time. Nothing built those binaries on Windows before a release. A new workflow builds the same seven the Windows archive holds, with the release job's directories, packages, features and --locked, in debug (which links each one): nightly, and on a push to main that changes a joule-code crate the archive builds from. Checked: joule-contrib type-checks and passes clippy -D warnings for x86_64-pc-windows-msvc, and its 33 lib tests pass natively (Thor). Changelog: none Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| crates | ||
| vendor/wtransport | ||
| Cargo.lock | ||
| Cargo.toml | ||