Wasmtime GitHub notifications bot (Oct 14 2025 at 18:34): Wasmtime GitHub notifications bot (Oct 14 2025 at 18:34):alexcrichton opened PR #11854 from alexcrichton:cargo-nextest to bytecodealliance:main:
See if we can reduce the number of shards we have without compromising on cycle time...
prtest:full
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Oct 14 2025 at 18:54):alexcrichton updated PR #11854.
Wasmtime GitHub notifications bot (Oct 14 2025 at 19:40):alexcrichton updated PR #11854.
Wasmtime GitHub notifications bot (Oct 14 2025 at 19:41):alexcrichton updated PR #11854.
Wasmtime GitHub notifications bot (Oct 14 2025 at 20:44):alexcrichton closed without merge PR #11854.
Wasmtime GitHub notifications bot (Oct 14 2025 at 20:44):alexcrichton commented on PR #11854:
hypothesis: by more evenly spreading out the test load across builders we could in theory get faster CI times and reduce the number of builders needed.
data shows: prior to this PR we build a subset of the tests for all builders, but now each builder builds the entire workspace. That takes a nontrivial amount of time and erases any possible gains, so doesn't seem worth it.
Last updated: Dec 06 2025 at 07:03 UTC