Increase resource limits for e2e-tests #382
Open
+5
−0
Conversation
This file contains hidden or 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
tnevrlka
force-pushed
the
e2e-tests-resources
branch
3 times, most recently
from
d00fdb0 to
236c6da
Compare
Contributor
Author
|
/retest |
3 similar comments
Contributor
Author
|
/retest |
Contributor
Author
|
/retest |
Contributor
Author
|
/retest |
tnevrlka
force-pushed
the
e2e-tests-resources
branch
2 times, most recently
from
2bf1829 to
7602ac8
Compare
MartinBasti
reviewed
Oct 17, 2025
prepare-e2e-tests and e2e-tests have recently started failing due to being OOMKilled. The task does pretty resource-intensive things so it makes sense to try to increase the limit. Signed-off-by: Tomáš Nevrlka <[email protected]>
tnevrlka
force-pushed
the
e2e-tests-resources
branch
from
7602ac8 to
75a8f09
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
prepare-e2e-tests task has recently started failing due to being OOMKilled.
The task does pretty resource-intensive things so it makes sense to try to increase the limit.