-
Notifications
You must be signed in to change notification settings - Fork 155
10.x: fix CI #836
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
10.x: fix CI #836
Conversation
35d584d
to
64e8c85
Compare
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.
utACK 64e8c85.
Fuzzer is still red because of some dependancy breakage in 10.x. But that is fine.
7af8c03
to
6658545
Compare
lol now the fuzzer is actually failing. I guess I ought to fix that and do another release.. |
6658545
to
32ea5da
Compare
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.
On 6658545 successfully ran local tests
32ea5da
to
2800fd5
Compare
Aside from being more future-proof, this also works with my local CI.
It may be that ubuntu-latest breaks us, but we're not doing anything particularly exotic so it seems unlikely. Meanwhile, our use of ubuntu-20.04 HAS broken us, because that runner is no longer supported. Meanwhile also update a bunch of our action versions to v4, since some of the v2s have become deprecated and removed. (Hopefully this won't happen very often.)
2800fd5
to
722e867
Compare
Weird that this only has an effect on a couple files, which aren't checked in the Github CI. Same story with 12.x.
As in rust-bitcoin#835, I changed a test function that used 'A'..'Z' to use an inclusive range, which is behavior-changing, and changed the impl of OrdF64::partial_cmp to be correct. Everything else is just syntactic. I apologize for structuring this PR very differently from rust-bitcoin#835 so you can't really range-diff. I tried rebasing and there were so many conflicts that I simply redid the whole thing, and since I had some experience I made some different decisions about what order to take things in.
Mostly removing &s.
This was at 1.58 to handle honggfuzz breakage; apparently it has to be 1.65 now.
This results in fuzzer crash when trying compute the checksum in `Display` implemenation of Descriptor Backport of 60fde9e from rust-bitcoin#569.
722e867
to
4842494
Compare
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.
On 4842494 successfully ran local tests
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.
Should get us green CI, and pins the nightly compiler version so that it stays green.