fix test flake by removing memory limit from test pod #2094
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
On AKS clusters, the pod's container would exceed its memory limit, get OOMKilled, get restarted, and cause that test to flake. Co-authored-by: Joshua Casey <joshuatcasey@gmail.com>
✅ Deploy Preview for pinniped-dev canceled.
|
joshuatcasey
approved these changes
Nov 6, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2094 +/- ##
==========================================
- Coverage 31.28% 31.27% -0.01%
==========================================
Files 371 371
Lines 61129 61129
==========================================
- Hits 19122 19121 -1
- Misses 41482 41484 +2
+ Partials 525 524 -1 ☔ View full report in Codecov by Sentry. |
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.
On AKS clusters, the pod's container would exceed its memory limit, get OOMKilled, get restarted, and cause that test to flake.
Release note: