[buildkite] Pause coverage reporting in buildkite pipeline tests #4314
Conversation
This file contains 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
|
@kentzeng12 I'm good with pausing for now, but let's get a fix in as well. Do we know the issue? |
andrewmains12
approved these changes
Nov 26, 2024
Unfortunately no, I am tracking this issue here: #4313. |
kentzeng12
force-pushed
the
zengk/pause_coverage
branch
from
bb5f76e to
1d7e64b
Compare
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.
What this PR does / why we need it:
Our pipeline tests are running really slowly on buildkite, example: https://buildkite.com/uberopensource/m3-monorepo-ci-uber-oss/builds/679. One reason is due to failing coverage reporting, which is causing the tests to sleep for 30 seconds repeatedly. This PR pauses coverage reporting, until we get a fix.
We are now averaging 14 mins to run all pipeline tests, down from 24 mins.
Fixes #4313
Does this PR introduce a user-facing and/or backwards incompatible change?:
No
Does this PR require updating code package or user-facing documentation?:
No