stop wrapping steps in runbld #96195
Merged
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
spalger
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
approved these changes
Apr 4, 2021
|
Steps seem to be running fine so I'm going to go ahead and merge this. |
spalger
added
the
auto-backport
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 4, 2021
Co-authored-by: spalger <[email protected]>
spalger
added a commit
that referenced
this pull request
Apr 4, 2021
Co-authored-by: spalger <[email protected]> Co-authored-by: Spencer <[email protected]> Co-authored-by: spalger <[email protected]>
⏳ Build in-progress, with failures
Failed CI StepsTo update your PR or re-run it, just comment with: |
💔 Build Failed
Failed CI StepsMetrics [docs]
To update your PR or re-run it, just comment with: |
spalger
added a commit
that referenced
this pull request
Apr 4, 2021
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.
We've been seeing a bunch of timeouts in CI and the best we can tell they're being caused by a networking issue that's halting the runbld which indexes the log output of ci steps in a central ES instance. It's troubling because none of our other CI instances is experiencing this, so this is a little bit of an experiment, but hoping this will give us more time to understand what is actually breaking and how we can fix it.