Eliah Kagan (@EliahKagan) This isn't the first time I have seen this failure mode.

Run cargo nextest run --workspace --no-fail-fast --exclude gix-error -- --skip fuzzed_timeout --skip performance --skip speed
error: no such command: `nextest`

help: a command with a similar name exists: `test`

help: view all installed commands with `cargo --list`
help: find a package to install `nextest` with `cargo search cargo-nextest`
Error: Process completed with exit code 1.

Just wanted to flag this in case you have some intuition about it - it's like there is a race between putting something in the PATH and being able to invoke it.

Just wanted to flag this in case you have some intuition about it

I vaguely recall reading that there was a bug in one of the actions we use in CI to install packages that intermittently causes it to fail silently to install a package on ARM64 Windows 11 systems--and that was fixed, but only recently. I don't know for sure whether this recollection is correct or not. I'll try to look into it.

I've upgraded install-action in #2517, which should fix the no such command: `nextest` error. See #2517 (review) for details.