chore: try switching to cargo nextest to speed up CI builds

[bolinfest]

I started looking at https://nexte.st/ because I was interested in a test harness that lets a test dynamically declare itself "skipped," which would be a nice alternative to this pattern:

codex/codex-rs/core/tests/suite/cli_stream.rs

Lines 22 to 27 in 4c46490

	if std::env::var(CODEX_SANDBOX_NETWORK_DISABLED_ENV_VAR).is_ok() {
	println!(
	"Skipping test because it cannot execute when network is disabled in a Codex sandbox."
	);
	return;
	}

ChatGPT pointed me at https://nexte.st/, which also claims to be "up to 3x as fast as cargo test." Locally, in codex-rs, I see

• cargo nextest run finishes in 19s
• cargo test finishes in 37s

Though looking at CI, the wins are quite as big, presumably because my laptop has more cores than our GitHub runners (which is a separate issue...). Comparing the CI jobs from this PR with that of a recent open PR:

	cargo test	cargo nextest
macos-14 - aarch64-apple-darwin	2m16s	1m51s
macos-14 - aarch64-apple-darwin	5m04s	3m44s
ubuntu-24.04 - x86_64-unknown-linux-musl	2m02s	1m56s
ubuntu-24.04-arm - aarch64-unknown-linux-musl	2m01s	1m35s
windows-latest - x86_64-pc-windows-msvc	3m07s	2m53s
windows-11-arm - aarch64-pc-windows-msvc	3m10s	2m45s

I thought that, to start, we would only make this change in CI before declaring it the "official" way for the team to run the test suite.

Though unfortunately, I do not believe that cargo nextest actually supports a dynamic skip feature, so I guess I'll have to keep looking? Some related discussions:

• https://internals.rust-lang.org/t/pre-rfc-skippable-tests/14611
• https://internals.rust-lang.org/t/skippable-tests/21260

[jif-oai]

Suggested change

	tool: nextest
	tool: nextest
	version: 0.9.103

Let's pin the version to prevent any malicious injections and prevent any risks if ok for you?

[bolinfest]

Pinned version for nextest and taiki-e/install-action

[bolinfest]

Yes: and should we also pin the GitHub action to a hash? I see your `cargo shear` or uses it as well?

…

On Mon, Sep 8, 2025 at 5:54 PM jif-oai ***@***.***> wrote: ***@***.**** approved this pull request. ------------------------------ In .github/workflows/rust-ci.yml <#3323 (comment)>: > @@ -160,12 +160,16 @@ jobs: find . -name Cargo.toml -mindepth 2 -maxdepth 2 -print0 \ | xargs -0 -n1 -I{} bash -c 'cd "$(dirname "{}")" && cargo check --profile ${{ matrix.profile }}' - - name: cargo test + - uses: ***@***.*** + with: + tool: nextest ⬇️ Suggested change - tool: nextest + tool: nextest + version: 0.9.103 Let's pin the version to prevent any malicious injections and prevent any risks if ok for you? — Reply to this email directly, view it on GitHub <#3323 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFAD7MQN2JYLGR2ZZYRO3T3RYQLVAVCNFSM6AAAAACF6LUK2GVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTCOJYGYZDONRTGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jif-oai]

I trust Github way more than a third-party maintained library but yes actually