Skip to content

[CI] TickerScheduleEngineTests testAddWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval failing #115339

@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:watcher:test" --tests "org.elasticsearch.xpack.watcher.trigger.schedule.engine.TickerScheduleEngineTests.testAddWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval" -Dtests.seed=3FF51600300F454D -Dtests.locale=ar-BH -Dtests.timezone=America/Rio_Branco -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] 3 consecutive failures in test testAddWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval
  • [8.x] 2 consecutive failures in step part-2
  • [8.x] 2 consecutive failures in step openjdk23_checkpart2_java-matrix
  • [8.x] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [8.x] 14 failures in test testAddWithNoLastCheckedTimeButHasActivationTimeExecutesBeforeInitialInterval (10.9% fail rate in 129 executions)
  • [8.x] 3 failures in step part2 (13.0% fail rate in 23 executions)
  • [8.x] 8 failures in step part-2 (20.5% fail rate in 39 executions)
  • [8.x] 2 failures in step openjdk23_checkpart2_java-matrix (100.0% fail rate in 2 executions)
  • [8.x] 3 failures in pipeline elasticsearch-intake (13.0% fail rate in 23 executions)
  • [8.x] 8 failures in pipeline elasticsearch-pull-request (24.2% fail rate in 33 executions)
  • [8.x] 2 failures in pipeline elasticsearch-periodic (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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions