Pin z3-solver on macOS VMs (backport #11408)
#11409
Merged
Conversation
This file contains 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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
mergify
bot
added
the
conflicts
|
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
github-actions
bot
added
type: qa
We currently use macOS 11.7 images in our CI and CPython 3.8 for the all-optionals test run. `z3-solver` recently released 4.12.3.0, which upped the macOS platform version from 10.16 to 11.7. This in theory should be fine for our VM image, but the pre-built version of CPython 3.8 we have access to was built for an older macOS, so does not match a `macos_11_7_x86_64` platform tag, and forces us to build Z3 from source, often timing out the job. This should have no effect on user machines, which will be typically be using newer versions of Python, or will be able to install from source if required. This CI-only constraint can be relaxed when the version of CPython we use on the macOS VMs supports the 11.7 macOS API version. (cherry picked from commit c865c56)
jakelishman
force-pushed
the
mergify/bp/stable/0.45/pr-11408
branch
from
f5a147f to
df83e11
Compare
jakelishman
approved these changes
Dec 13, 2023
jakelishman
removed
the
conflicts
|
@Mergifyio backport stable/0.46 |
✅ Backports have been created
|
Pull Request Test Coverage Report for Build 7199022876
💛 - Coveralls |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
mergify bot
added a commit
that referenced
this pull request
Dec 14, 2023
We currently use macOS 11.7 images in our CI and CPython 3.8 for the all-optionals test run. `z3-solver` recently released 4.12.3.0, which upped the macOS platform version from 10.16 to 11.7. This in theory should be fine for our VM image, but the pre-built version of CPython 3.8 we have access to was built for an older macOS, so does not match a `macos_11_7_x86_64` platform tag, and forces us to build Z3 from source, often timing out the job. This should have no effect on user machines, which will be typically be using newer versions of Python, or will be able to install from source if required. This CI-only constraint can be relaxed when the version of CPython we use on the macOS VMs supports the 11.7 macOS API version. (cherry picked from commit c865c56) Co-authored-by: Jake Lishman <[email protected]> (cherry picked from commit ef21b50)
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 14, 2023
We currently use macOS 11.7 images in our CI and CPython 3.8 for the all-optionals test run. `z3-solver` recently released 4.12.3.0, which upped the macOS platform version from 10.16 to 11.7. This in theory should be fine for our VM image, but the pre-built version of CPython 3.8 we have access to was built for an older macOS, so does not match a `macos_11_7_x86_64` platform tag, and forces us to build Z3 from source, often timing out the job. This should have no effect on user machines, which will be typically be using newer versions of Python, or will be able to install from source if required. This CI-only constraint can be relaxed when the version of CPython we use on the macOS VMs supports the 11.7 macOS API version. (cherry picked from commit c865c56) Co-authored-by: Jake Lishman <[email protected]> (cherry picked from commit ef21b50) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an automatic backport of pull request #11408 done by Mergify.
Cherry-pick of c865c56 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com