regenerate cargo.lock to fix pipeline#5251
Open
jantimon wants to merge 1 commit intofacebook:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
it looks like commit 197db55 by bumped
randfrom 0.9 to 0.10 (and touchedrelay-lsp) but did not regeneratecompiler/Cargo.locknow the main branch pipeline fails because CI runs
cargo test --lockedandcargo run --releasefor the test-project build errors withcannot update the lock file /.../compiler/Cargo.lock because --locked was passedI ran
cargo update -p rand -p hyperto sync the lockfile (hyper 1.8.1 → 1.9.0 was also stale from an earlier commit) and verified locally thatcargo test --manifest-path=compiler/Cargo.toml --lockedbuilds cleanly and the working tree stays clean afterwards