DO NOT MERGE! Parallelize podman build tests #24645
Conversation
DO NOT MERGE! Seriously, like don't even fantasize about it until containers/buildah#5674 is fixed and the fix is vendored into podman. I am filing this because if/when that happens, this PR will give you a nice CI-runtime boost. I spent a good chunk of time identifying the tests which can / can't be parallelized in this module. Hope it helps some day. Signed-off-by: Ed Santiago <[email protected]>
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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-sigs/prow repository. |
openshift-ci
bot
added
the
do-not-merge/release-note-label-needed
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago 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 |
openshift-ci
bot
added
approved
edsantiago
added
do-not-merge/blocked-paths
|
In a completely unrelated note, i see we have a do-not-merge/cherry-pick-not-approved and I think that sounds useful for @TomSweeneyRedHat so probably worth figuring out how it works |
DO NOT MERGE! Seriously, like don't even fantasize about it
until containers/buildah#5674 is
fixed and the fix is vendored into podman.
I am filing this because if/when that happens, this PR will
give you a nice CI-runtime boost. I spent a good chunk of
time identifying the tests which can / can't be parallelized
in this module. Hope it helps some day.
Signed-off-by: Ed Santiago [email protected]
Not adding a release note because I want as many red do-not-merge blocks as possible