Repository navigation
[CI] EsqlActionBreakerIT class failing #114194
Copy link
Copy link
Closed
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)medium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releases
Description
Activity
- added:Analytics/ES|QLAKA ESQLAKA ESQL>test-failureTriaged test failures from CITriaged test failures from CI
on Oct 6, 2024 - added a commit that references this issue
on Oct 6, 2024 elasticsearchmachine commented
on Oct 6, 2024 CollaboratorAuthorMore actionsThis has been muted on branch main
Mute Reasons:
- [main] 4 failures in class org.elasticsearch.xpack.esql.action.EsqlActionBreakerIT (0.6% fail rate in 713 executions)
- [main] 2 failures in step part-3 (0.8% fail rate in 247 executions)
- [main] 2 failures in pipeline elasticsearch-periodic-platform-support (14.3% fail rate in 14 executions)
- [main] 2 failures in pipeline elasticsearch-pull-request (0.8% fail rate in 251 executions)
Build Scans:
- addedTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)needs:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
on Oct 6, 2024 elasticsearchmachine commented
on Oct 6, 2024 CollaboratorAuthorMore actionsPinging @elastic/es-analytical-engine (Team:Analytics)
- addedmedium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releasesand removedneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
on Oct 7, 2024 Update:
I can't reproduce it. Some things I tried:
- Testing in the failing commit with and without the given seeds
- Testing in main with and without the given seeds
- In case it was related to these last TDigest/CB PRs (Add CircuitBreaker to TDigest, Step 4: Take into account shallow classes size #113613), I tried to run the
testGroupingMultiValueByOrdinalstest (The only one using TDigest, via the Percentile function) with an adapted version ofEsqlActionBreakerIT#runWithBreakingwith the complete range of CB limits (From 256 to 2048), with no result
Added the
medium-risktag as it disabled the full suite, and given many tests are failing within it, I don't think I can safely limit the muted methods- added a commit that references this issue
on Oct 10, 2024 - added a commit that references this issue
on Oct 11, 2024 - added a commit that references this issue
on Oct 13, 2024
Metadata
Metadata
Assignees
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)medium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releases
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.