-
Notifications
You must be signed in to change notification settings - Fork 780
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): update dependency containers/automation_images to v20230614 #4772
Conversation
04889a5
to
bfab50e
Compare
@nalind any idea what this smoke test (log) error means:
|
a072748
to
c60a7ee
Compare
Update: Found golangci/golangci-lint#3414 (comment) Edit: Renovate is already proposing this in another PR. |
c60a7ee
to
0cd2330
Compare
Force-push: Attempt to update tooling modules. |
Ugh...this is some incredible rabbit-hole I've worked myself into 😢 @containers/buildah-maintainers Heeeeeeeeeeelp! I really don't know what to do here. It seems that golangci-lint is in desperate need of an update b/c golang 1.20 in F38. However, fixing that (clearly) opens a giant can-o-worms 😭 To summarize:
|
182a9fb
to
00b1bf3
Compare
00b1bf3
to
182a9fb
Compare
Force-push: Restoring my updates. I don't understand why Renovate insists on overwriting my changes every 24h. Can't find a setting to disable that 😞 |
182a9fb
to
606b0ed
Compare
Force-push: Rebased and updated CI VM images (slightly). |
@flouthoc any news fixing this, good or bad? |
606b0ed
to
42e40cc
Compare
42e40cc
to
99882ba
Compare
Force-push: Bumped image up to |
@nalind PTAL at these conformance test failures. At a glance, it seems all/most are failing due to file-permission differences in docker. Like Docker's dropping the most-significant bits or something:
Any idea what's going on? Was there a recent change in docker that caused this maybe? |
@flouthoc in the unit tests, I'm still seeing a few failures. But there's also a HUGE number of errors like the following. Is this related to the tooling re-vendoring?
|
@rhatdan there's an interesting SELinux test failure happening. Is this caused by recent work on container-selinux packages?
|
Yes. |
I will take this over. |
Thanks Dan, sorry it's such a huge mess 😕 |
I looked at this for a while yesterday, and I have no idea why it is happening. The test fails locally in a very unexpected manner, and I believe the problem is in container-selinux, although I have not figured out what it is yet. |
Thanks for trying so hard Dan. At least the problem is reproducible. Idea: If you want to simplify the number of changes for debugging, but still run on F38, you could temporarily bypass all calls to build or run golangci-lint. That's the main thing leading to the mass re-vendoring of |
Thanks @flouthoc that helps a lot actually. @rhatdan I believe you've been working/fighting/struggling to fix this for quite a while now. I think maybe the larger buildah-CI beneficiary's may be suffering due to lack of F38 testing. Would you be comfortable if we skip these failing tests temporarily? |
If the only thing that is failing is the SELinux tests, then skip and I will look at them. I thought the problem was the conformance tests. |
Also update Fedora and Debian names. Signed-off-by: Renovate Bot <bot@renovateapp.com> Signed-off-by: Chris Evich <cevich@redhat.com>
4e4ea40
to
950bd91
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: renovate[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Ack, thanks. Just rebased/force-pushed to confirm that's all that's failing. |
Conformance tests are failing because it is comparing: buildah's attribute including both Anyways I think this should be easy to fix. ( at least that what it seems from looking at it ) |
Should we change to match Docker, or continue with what we are doing and adjust the test? |
My un-educated opinion is we should just adjust the test. I think I remember seeing this class for failure several times before (likely during CI VM updates). So I suspect that chasing after docker may be a frequent PITA w/o much actual benefit. Though I'm certainly not an expert on these things. |
We should probably match Docker's removal of |
Fixes for containers/buildah#4772 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Fixes for containers/buildah#4772 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Fixes for containers/buildah#4772 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Fixes for containers/buildah#4772 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
950bd91
to
a135001
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 20230614.x releases. But if you manually upgrade to 20230614.x then Renovate will re-enable If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
(Assuming closing this was on accident) |
a135001
to
950bd91
Compare
Force-push: Restoring (customized) commits. |
We are getting close on the SELinux PR above, so closing. |
Ahh good news, thanks for the detail Dan. |
This PR contains the following updates:
20230405t152256z-f37f36d12
->20230614t132754z-f38f37d13
Release Notes
containers/automation_images (containers/automation_images)
v20230614t132754z-f38f37d13
Compare Source
v20230601t145439z-f38f37d12
Compare Source
v20230517t144652z-f38f37d12
Compare Source
v20230426t140447z-f38f37d12
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.