packit: disable Centos Stream/fedora ELN teasks #24083
Conversation
The go version there is only go 1.22.5 but we need go 1.22.6 as of containers#24054 It is not clear to me how to best monitor the repos there to see when they get the update. And then there is the fear that podman keeps updating faster then these envs which makes testing there immposible[1] [1] containers/image#2550 (comment) Signed-off-by: Paul Holzinger <[email protected]>
openshift-ci
bot
added
release-note-none
approved
|
@lsm5 PTAL, not sure if this is a good idea (especially the propose downstream for cs10) but I rather not see the failed tests on every PR. |
There was a problem hiding this comment.
I'm told the golang version on centos stream issue should be resolved soon. And this is going into main so shouldn't be a problem.
I'm still looking into how best to monitor repos. copr cli doesn't have anything built in. I think pkgdb-cli or koji/bodhi could be useful, but we can leave that for later.
/lgtm
/approve
/hold
openshift-ci
bot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, Luap99 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 |
Luap99
added
the
No New Tests
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
@lsm5 https://composes.stream.centos.org/stream-10/development/latest-CentOS-Stream/compose/AppStream/x86_64/os/Packages/ has golang 1.23.1, so I suppose this could be re-enabled? I'm asking because someone from the podman team asked us to enable c-podman testing for podman PRs on CentOS. Happy to do that, but we first need podman builds for that. |
I'll look into that.
That someone was me :) . Thanks for taking this up. I'll let you know once we have green builds. |
The go version there is only go 1.22.5 but we need go 1.22.6 as of #24054
It is not clear to me how to best monitor the repos there to see when they get the update. And then there is the fear that podman keeps updating faster then these envs which makes testing there immposible[1]
[1] containers/image#2550 (comment)
Does this PR introduce a user-facing change?