-
Notifications
You must be signed in to change notification settings - Fork 831
CI: Fx pinning #2036
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
CI: Fx pinning #2036
Conversation
More crates broke our MSRV by using edition 2021 without doing a major release, pin them in the CI script. diff --git a/contrib/test.sh b/contrib/test.sh index 74f8ffb..79932ad 100755 --- a/contrib/test.sh +++ b/contrib/test.sh @@ -13,6 +13,12 @@ if cargo --version | grep ${MSRV}; then cargo update -p quote --precise 1.0.30 cargo update -p proc-macro2 --precise 1.0.63 cargo update -p serde_test --precise 1.0.175 + # Have to pin this so we can pin `schemars_derive` + cargo update -p schemars --precise 0.8.12 + # schemars_derive 0.8.13 uses edition 2021 + cargo update -p schemars_derive --precise 0.8.12 + # memcrh 2.6.0 uses edition 2021 + cargo update -p memchr --precise 2.5.0 cargo update -p bitcoin:0.30.1 --precise 0.30.0
d2b0644
to
adcc01c
Compare
I'm not able to reproduce the CI failure locally. What am I missing? checkout 08-29-improve-witness-display:
pin deps from README
run cargo check
results
|
Sorry bro, I already spend too much time pinning crates to debug your local repro. It can be seen by the all-green CI that this works and the red 1.48 job in most every other open PR that this is currently broken. Can we get a second ACK please crew so this can go in. cc @TheBlueMatt because you mentioned your CI was broken here: #2034 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified it crashes pre-patch and does not crash post-crash on toolchain 1.48
tACK
@yancyribbens You need to delete Cargo.lock and ./target/ folder after you switch your local toolchain to 1.48 Then try it again from the beginning. |
@junderw oops thanks. I figured it was something obvious I forgot about. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK adcc01c
I feel we are short on reviewers. I will merge this tomorrow if we don't get ACKs |
I feel we should just merge MSRV CI fixes without waiting for 2 ACKs rule. It stalls development and review for all other PRs. |
I agree, the 2 ack policy is not useful for CI changes in general but especially when CI is broken for other PRs. |
I agree. 1 ACK should be enough for CI / testing fixes. |
I wouldn't mind making this explicit in our policy -- I made the same call in some recent PR (which I can't find now). I think if something only touches CI, or only makes grammatical changes to docs (I'm open to other suggestions but let's make them explicit non-judgement-call ones) then it's fine to merge with 1 ACK and no delay. |
More crates broke our MSRV by using edition 2021 without doing a major release, pin them in the CI script.
Other open PRs need this to get past CI.