Use ubuntu-latest-16-cores from CNCF for e2e #1786
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SaschaSchwarze0
added
the
kind/failing-test
openshift-ci
bot
added
the
do-not-merge/work-in-progress
pull-request-size
bot
added
the
size/XS
openshift-ci
bot
added
the
release-note-none
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
SaschaSchwarze0
force-pushed
the
sascha-ubuntu-latest-16-cores-e2e
branch
from
e80d22e to
d24638a
Compare
pull-request-size
bot
added
size/S
SaschaSchwarze0
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
SaschaSchwarze0
added
kind/flake
4 tasks
adambkaplan
approved these changes
Jan 27, 2025
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan 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
the
approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
In e2e we had disk space issues and therefore used the maximize-build-space action. We still sometimes had failures and with the more complex cluster setup needed in #1711, we need again more disk space.
Switching to the larger custom runners that we get from CNCF for e2e tests. They have more than 500 G disk space, that will be enough for us.
With the additional compute power, e2e completes in ≈ 21 minutes instead of ≈ 35 minutes. (We run ginkgo with
-pwithout any explicit parallism. It automatically used 15. See "Running in parallel across 15 processes" in logs, the default workers had just 4).Submitter Checklist
Release Notes