-
Notifications
You must be signed in to change notification settings - Fork 276
Fix z3 in CI for restored c2rust-refactor #1388
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
Fix z3 in CI for restored c2rust-refactor #1388
Conversation
ed3d3a4
to
d48ad20
Compare
Don't we also have a problem on mac OS? I couldn't figure out how to solve that one. |
Couldn't this have been a pull request from #1328, so it only shows your new commits? |
I mean, I can cherry-pick your fixes once they work, but PR-against-PR might have been cleaner. |
I just opened a PR to run CI; I can set target to your branch if you want. I wasn't sure if this would need a rebase/etc. first and wanted to avoid noise in the original PR, or I would have just pushed to that branch. |
Just nitpicking and trying to make our lives easier, appreciate the help! I'm not sure when I'll get around to rebase my original branch, but I could roll your fixes into it once they pass CI. |
Despite GH's claims to the contrary, a simple |
9d5e834
to
e64801b
Compare
macOS CI now works... but for some reason the testsuite is broken. |
e2fbf8c
to
82f1cc2
Compare
e2fbf8c failed the z3 test claiming quickcheck failed:
Upon further investigation, it looks like this is a real test failure, but not macOS-related. That CI run just got lucky with quickcheck seeds. I'll submit a follow-up PR. |
b68e96b
to
2f656bb
Compare
2f656bb
to
b2cd4eb
Compare
I think this requires less fiddly setup with newer versions of the
z3
crate, but we can't use those because they switch to the 2024 edition, which our pinned nightly from 2023 doesn't know about.