Skip to content
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

chore(deps): bump z3 to 4.13.0 #15413

Closed
wants to merge 1 commit into from

Conversation

chenrui333
Copy link

Signed-off-by: Rui Chen <rui@chenrui.dev>
Copy link

github-actions bot commented Sep 7, 2024

Thank you for your contribution to the Solidity compiler! A team member will follow up shortly.

If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother.

If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix.

@cameel
Copy link
Member

cameel commented Sep 8, 2024

The procedure to update z3 is unfortunately a bit more complicated than this. It will require updating test expectations, and AFAIK Z3Prover/z3#7255 is still a blocker for this (@blishko is that still the case?).

It also cannot be easily done in an external PR, since we need the PR to trigger the base CI image rebuild via Github Actions. For this reason I'm going to close this. We still have #15198 open though, and we do intend to update when blockers are resolved.

@chenrui333
Copy link
Author

@cameel got it, do you have any concerns that homebrew ship the binary built with z3 4.13.0 then? thanks!

@cameel
Copy link
Member

cameel commented Sep 9, 2024

Not really. The Z3 issue is about it hanging in some scenarios, but the output is still correct when you do get an answer. 4.12 might be a better choice if you hit those hanging cases but 4.13 has some improvements and bugfixes too so I can't even say that one is recommended over the other. Both versions are supported, we still support anything >= 4.8, it's just that 4.12 is still the one we run our tests against. The STRICT_Z3_VERSION option forces that specific version by default, but it can be disabled and is there mostly to guide people who don't have a strong preference to choose the one that can pass the test suite, which is unfortunately bound to a single version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants