-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(deps): update common, image, and storage deps #18510
Conversation
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.
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
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe, renovate[bot], rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Restarted flaked job
go.mod
Outdated
github.com/containers/conmon v2.0.20+incompatible | ||
github.com/containers/image/v5 v5.25.1-0.20230505072505-dc4a4be9cc1e | ||
github.com/containers/libhvee v0.0.5 | ||
github.com/containers/ocicrypt v1.1.7 | ||
github.com/containers/psgo v1.8.0 | ||
github.com/containers/storage v1.46.1 | ||
github.com/containers/storage v1.46.2-0.20230508110141-51c23d59f8f3 |
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.
The Debian job keeps failing. @nalind could something in storage have caused the jobs to fail? Curious that it only happens on Debian.
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.
It doesn't appear to be interacting well with the version of buildah in the VM (1.28.2), though I can't trigger the same error when I run relevant specific integration test scripts in a manually-started VM.
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.
@nalind Do we have to update the buildah version in the debian VM ?
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.
Do we know which version that is?
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.
No I am not sure about it, @cevich Could help us in confirming the version of buildah in debian VM
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.
You can always use hack/get_ci_vm.sh
to check and reproduce if needed.
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.
That is, in fact, how I manually started the VM in which I wasn't able to reproduce the issue.
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.
Ok this is very weird then.
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.
It's 1.28.2+ds1-1+b3
in the c20230426t140447z-f38f37d12
image. I've got a fresh set of images building as I write this in case it helps.
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.
Just checked the new image as it was building. It has a slightly newer 1.28.2+ds1-3
.
Restarted test. |
Apparently this matters, see containers#18510 (comment) Signed-off-by: Chris Evich <[email protected]>
0af4285
to
25b7d75
Compare
New changes are detected. LGTM label has been removed. |
59bf47d
to
c4d488c
Compare
okay, I checked the "renovate please rebase this" button. |
c4d488c
to
0fbd593
Compare
0fbd593
to
5c8ac9d
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
5c8ac9d
to
b32a5cc
Compare
Tests are breaking here! I did a brief skim and apart from flakes one common factor seems to be a missing |
Yes, c/image is now not saying It’s a purely aesthetic thing, so if this were a deadline blocker or something, I’m fine with temporarily reverting that. OTOH I do think it’s a move in the right direction overall, so past the immediate short-term concerns I’d prefer the tests to be updated if they expect that output. Do you need me to help with the test update? |
If fixing the test is the right thing then I can do it, I just wanted an ack from you. |
I believe the tests should be fixed. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR contains the following updates:
586a3be
->6eebb37
07ced61
->dc6d2c8
cc0d208
->73f2995
Configuration
📅 Schedule: Branch creation - "before 11am" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.