-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Closed
Labels
:mlMachine learningMachine learning>test-failureTriaged test failures from CITriaged test failures from CITeam:MLMeta label for the ML teamMeta label for the ML teammedium-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
Build Scans:
Reproduction Line:
./gradlew ":x-pack:plugin:core:test" --tests "org.elasticsearch.xpack.core.ml.job.config.DetectionRuleTests.testEqualsAndHashcode" -Dtests.seed=B7D0A8305C244ED1 -Dtests.locale=es-SV -Dtests.timezone=HST -Druntime.java=22
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
org.elasticsearch.ElasticsearchStatusException: Invalid detector rule: actions do not contain force_time_shift, but corresponding parameters are present
Issue Reasons:
- [main] 2 consecutive failures in step part2
- [main] 2 consecutive failures in pipeline elasticsearch-intake
- [main] 2 failures in test testEqualsAndHashcode (1.1% fail rate in 174 executions)
- [main] 2 failures in step part2 (5.9% fail rate in 34 executions)
- [main] 2 failures in pipeline elasticsearch-intake (5.9% fail rate in 34 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
Labels
:mlMachine learningMachine learning>test-failureTriaged test failures from CITriaged test failures from CITeam:MLMeta label for the ML teamMeta label for the ML teammedium-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