ci: reduce flakiness and optimize resources#65
Merged
Conversation
Contributor
Author
|
/ci |
Contributor
Contributor
Contributor
Author
|
Interesting. Log collection succeeded but validation failed. Possibly due to corrupted archives. I'm going to re-run the CI to see if its a flake |
Contributor
Author
|
/ci |
2 similar comments
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
Contributor
Contributor
Contributor
Author
|
CI failing cuz there seems to be an on-going github outage: Will retry in a bit |
Contributor
Author
|
/ci |
Contributor
Contributor
Contributor
Author
|
/ci |
Contributor
shvbsle
changed the title
Contributor
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
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.
Issue #, if available:
Flaky runs: workflow
Description of changes:
Reduce e2e cluster from 3 nodes to 1. On a multi-node cluster, only the node running system pods (CoreDNS, etc.) has VPC CNI IPAMD allocations, so
/var/run/aws-node/ipam.jsondoesn't exist on idle nodes. The IPAMD log collector records this as an error inlog-capture-errors.log, whichassertLogsValidtreats as a test failure. A single node runs all system pods and will always have the IPAMD checkpoint file. This also reduces CI compute costs. We don't need 3 nodes to validate NMA behavior.Testing Done:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.