chore(e2e): fix flaky test & standalone behavior#11382
Merged
milas merged 1 commit intodocker:mainfrom Jan 30, 2024
Merged
Conversation
This test was flaking in CI even though it was succeeding; I think there's a race with us killing and getting the output. Regardless, refactored so that it watches the process, which should make the test more reliable and faster. Additionally, I noticed that the standalone config was incorrect, so I (reset) the bool to the correct value to ensure we test things in plugin mode for E2E. Signed-off-by: Milas Bowman <[email protected]>
glours
requested review from
a team,
jhrotko and
ndeloof
and removed request for
a team
rarguelloF
pushed a commit
to rarguelloF/compose
that referenced
this pull request
Mar 15, 2024
temenuzhka-thede
pushed a commit
to temenuzhka-thede/compose
that referenced
this pull request
Sep 17, 2024
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
3 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.
What I did
This test was flaking in CI even though it was succeeding; I think there's a race with us killing and getting the output. Regardless, refactored so that it watches the process, which should make the test more reliable and faster.
Additionally, I noticed that the standalone config was incorrect, so I (reset) the bool to the correct value to ensure we test things in plugin mode for E2E.
Related issue
n/a
(not mandatory) A picture of a cute animal, if possible in relation to what you did
