[CI] TickerScheduleEngineTests testWatchWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval failing #115368
Description
Build Scans:
- elasticsearch-intake #11772 / part2
- elasticsearch-pull-request #38045 / part-2
- elasticsearch-pull-request #38000 / part-2
- elasticsearch-pull-request #37975 / part-2
- elasticsearch-periodic-platform-support #4516 / rhel-9_platform-support-unix
- elasticsearch-periodic #4544 / openjdk23_checkpart2_java-matrix
- elasticsearch-intake #11715 / part2
- elasticsearch-pull-request #37867 / part-2-fips
- elasticsearch-pull-request #37861 / part-2
- elasticsearch-periodic-platform-support #4511 / ubuntu-2004-aarch64_checkpart2_platform-support-arm
Reproduction Line:
./gradlew ":x-pack:plugin:watcher:test" --tests "org.elasticsearch.xpack.watcher.trigger.schedule.engine.TickerScheduleEngineTests.testWatchWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval" -Dtests.seed=59319C7AAF58A9C7 -Dtests.locale=yo-BJ -Dtests.timezone=America/Menominee -Druntime.java=23
Applicable branches:
8.x
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
java.lang.AssertionError:
Expected: is <2>
but: was <1>
Issue Reasons:
- [8.x] 13 failures in test testWatchWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval (9.0% fail rate in 145 executions)
- [8.x] 2 failures in step part2 (6.7% fail rate in 30 executions)
- [8.x] 7 failures in step part-2 (14.9% fail rate in 47 executions)
- [8.x] 2 failures in pipeline elasticsearch-intake (6.7% fail rate in 30 executions)
- [8.x] 8 failures in pipeline elasticsearch-pull-request (19.0% fail rate in 42 executions)
- [8.x] 2 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 2 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.