-
Notifications
You must be signed in to change notification settings - Fork 2.1k
ci(actions): ensure cargo check with frozen lockfile #3388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
b80f250
to
decf916
Compare
Benchmark for 4facc39Click to view benchmark
|
🟢 CI successful 🟢Thanks |
Benchmark for b9c558eClick to view benchmark
|
@kwonoj I had to revert that. I think that's a good idea, but it broke CI. Not even this PR passed the CI. Maybe you want to use |
@sokra weird, --frozen is alias to --locked. https://doc.rust-lang.org/cargo/commands/cargo-build.html#manifest-option Also PR correctly passed ci. Ref: https://github.com/vercel/turbo/actions/runs/3963353615/jobs/6792718578 |
Looks like |
hmm... weird... This one didn't pass: https://github.com/vercel/turbo/actions/runs/3964721165/jobs/6793846772 |
It seem to complain about not being about to make network requests. I guess it need to make requests when it need to download the crates from the registry. Maybe it only passes with rust cache, but fails on downloading when there is no cache or crates are missing... |
retry #3388 with `--locked` instead of `--frozen`
Avoid cases like #3387