-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Bump docker images for z3 4.8.10 #10844
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
Conversation
|
|
|
|
|
|
|
|
cameel
left a 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.
Looks fine. The archlinux test job is failing because CI is still using the old images with Z3 4.8.9, right?
|
@cameel nop, arch installs directly from |
|
Ah no, the images are fine. I need to copy the hashes in the comments here into #10845, and the tests should pass there. Only after merging that we should merge this one. |
#10845 needs to pass tests first after all.
874f9df to
5ba21c7
Compare
2badaae to
d416d05
Compare
5ba21c7 to
da08fa4
Compare
d416d05 to
5c76697
Compare
|
|
|
|
| #------------------------------------------------------------------------------ | ||
| FROM buildpack-deps:focal AS base | ||
| LABEL version="4" | ||
| LABEL version="5" |
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.
Same as above.
|
|
|
|
bshastry
left a 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.
LGTM. Failing test should pass in the other PR but better to update that PR with the docker image hash published by the bot in that PR and verify this before merging this PR.
5c76697 to
fbfcb4e
Compare
cameel
left a 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.
Should be good to merge as soon as tests pass.
|
I'm slightly worried that the docker images are being built again, this shouldn't be the case... if it is, the hashes are gonna be different and we'll have to do the other PR again |
|
Ah, right. That's because you rebased it. They will almost certainly be different unless it's using Docker's cache (and I don't think it is because the build machine is not persistent). I remember that last time @aarlt was updating the images, he put the PR using the hashes on top of the one building the images. Looks like that was a better strategy. Anyway, the images that were already built should be good so I think all tests will pass anyway, even if you do not take the new hashes. |
|
Yea, I cancelled the new builds so we don't have trash lying around, but should be good |
Once the images are built, their hashes will be used by the PR that updates the tests.