LukeMathWalker / LukeMathWalker/cargo-chef
Nextest compiles all the deps
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I would like to make use of cargo-chief in the CI for unit tests stage, so I've prepared the docker image for the CI pipeline containing following two directives:
```
RUN cargo chef cook --clippy --all-targets --all-features --recipe-path recipe.json
RUN cargo chef cook --tests --benches --all-features --recipe-path recipe.json
```
In the pipeline I copy all the sources into the /app directory (where commands above took place) and run the CI commands. Clippy stage works like a charm - only my project is checked. When it comes to the unit test stage it runs the following command:
`cargo nextest run --all-features --profile ci --config-file=.cargo/nextest.toml`
But it does the compilation of all the dependencies. Only the downloading is skipped.
I wonder if I'm doing something wrong or nextest is incompatible with the cargo-chief?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the CI flow using the Docker image, recipe.json, and .cargo/nextest.toml; compare the cargo chef cook commands with the cargo nextest run command. Check whether dependency compilation is expected or indicates incompatible cache metadata, and document the cause or provide a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100