Repository navigation
add cargo-nextest 0.9.145 - #720
Conversation
Builds only the cargo-nextest workspace member with upstream's distributor feature set (--no-default-features --features default-no-update), dropping the self-update code that has no place under a package manager. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Warning Review paused — included plan limit reachedKeep your review moving with free on-demand reviews.
On-demand reviews are free for the next 2 days.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Promotion and pricing detailsOn-demand reviews are free for the next 2 days. After that, they cost $0.25 per reviewed file. Review limit detailsOr wait 59 minutes for your next included review. Limit details: You’ve used the included review currently available. Your 62 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (2)
Comment |
|
Reproducibility proof (mip 0.5.5-dev.49.gcb384e31, the Note the PR |
…test (#1551) gominimal/pkgs#720 added cargo-nextest 0.9.145, merged as f4de33d0. Every `test:` line the agent runtime runs for a task is `cargo nextest run …`, and it runs them in a sandbox that carries only its base set plus this file's `[session] packages`; with no nextest there, every task's tests fail before they compile and every pull request opens as a draft. The pin moves 65 pkgs commits (ff15baa9 → f4de33d0). That is the toolchain too — gcc, glibc, binutils, openssl, zlib, linux_headers, protobuf, skopeo, curl, and the virtio kernel and rootfs the VM outputs build from — so the dogfood and KVM lanes on this change are the proof, not this message. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Summary
Adds
cargo-nextest, the next-generation Rust test runner (per-test process isolation, parallel execution, retries, JUnit output). 0.9.145 is the latest upstream release.Only the
cargo-nextestworkspace member is built, with upstream's documented distributor feature set (--no-default-features --features default-no-update). That drops the self-update code path, which has no place under a package manager, and its dialoguer/TLS dependencies with it.Changes
packages/cargo-nextestat upstream version 0.9.145, sourcehttps://github.com/nextest-rs/nextest/archive/refs/tags/cargo-nextest-0.9.145.tar.gz.CARGO_INCREMENTAL=0,-C linker=gcc,--remap-path-prefixfor the build dir and cargo home,--locked.glibc,libgcc.cargo-nextest nextest --versionand--help.Checklist
min checkpasses for the affected packages/harnesses.min package build cargo-nextestsucceeds (patched-build failed locally on a stale cached glibc predating the 2.44 pin, unrelated to this package).source_provenancepoints to the canonical upstream and the source builds from source (not a prebuilt release binary) where the required toolchain is available.Notes for reviewers
mip package build --rebuild cargo-nextest, mip 0.5.5-dev.49, arm64) produced byte-identical trees:diff -rclean,usr/bin/cargo-nextestsha2561a85de12…c5efbboth times. See the comment below. The source tarball carries no.gitand nonextest-commit-info, sobuild.rsembeds no commit hash.usdtfeature (part ofdefault-no-update) compiles DTrace probe points; inert on Linux without a consumer.🤖 Generated with Claude Code