PoC: split mandatory from other stages #24790
Closed
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
botelastic
bot
added
the
needs_team
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 1 |
| Passed | 2395 |
| Skipped | 3 |
| Total | 2399 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
TestMonitorSample – github.com/elastic/beats/v7/libbeat/metric/system/cpu
|
/test ext auditbeat |
|
/test |
…eline * upstream/master: CI: curl seems to be available but where cannot find it (elastic#24965) [mergify] backport automation to 7.x, 7.12 and 7.11 (elastic#24608) Only show deprecation warnings for CN-based verification once (elastic#24948) CI: use ubuntu-20 (elastic#24963) Debug empty root field instead of error (elastic#24966) Kubernetes_secrets provider improvements (elastic#24912)
|
/test |
v1v
added
Team:Automation
|
/test |
2 similar comments
|
/test |
|
/test |
|
I'm tempted to close this implementation which was quite intrusive compare to the new one |
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 does this PR do?
Split the pipeline in three meta-stages:
From the user point of view, this could help to discard flakiness and trigger the specific stage:
/test <beats>runs the first stage/test ext <beats>runs the second stage.Why is it important?
Explore a way to improve the flakiness by splitting what's stable versus what's a bit more flaky.
Potentially, this will reduce the CI load by provisioning less number of workers in parallel, which at the moment is causing issues with timeouts. This should help to smooth the required CI workers in batches and affecting a bit less the other pipelines.