Revert "Switch coverage CI targets to EngFlow (#39269)"#39299
Merged
phlax merged 1 commit intoenvoyproxy:mainfrom May 1, 2025
Merged
Revert "Switch coverage CI targets to EngFlow (#39269)"#39299phlax merged 1 commit intoenvoyproxy:mainfrom
phlax merged 1 commit intoenvoyproxy:mainfrom
Conversation
This reverts commit e0420ee. It unexpectedly resulted in lower coverage numbers - we should rollback while we are investigating what's going on to avoid disruptions. Signed-off-by: Mikhail Krinkin <mkrinkin@microsoft.com>
krinkinmu
force-pushed
the
rollback-eng-flow
branch
from
2542edb to
8e4adee
Compare
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.
Commit Message:
This reverts commit e0420ee. It unexpectedly resulted in lower coverage numbers - we should rollback while we are investigating what's going on to avoid disruptions.
Additional Description:
Some relevant discussions can be found in #39030 which prompted me to work on this in the first place. And I will use #39248 as a tracking bug for the coverage changes.
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a
+cc @phlax