Zane/node level test coverage#1673
Merged
Merged
Conversation
rashmichandrashekar
approved these changes
May 9, 2026
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
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.
why this pr?
when there are multiple nodes, e2e will pass as long as at least one ama-logs pod emit logs.
we now have a cluster with different node pools added to build pipeline. this pr ensures all nodes must have logs in order to pass e2e tests.
cluster with different nodes
Docker-Provider/.pipelines/azure_pipeline_mergedbranches.yaml
Lines 1040 to 1051 in 3bb5c30
tested by running ginko test on my own cluster with the flag and without flag.