Skip to content

[CI] TestClustersPluginFuncTest override jdk usage via ES_JAVA_HOME for known jdk os incompatibilities failing #135413

@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

null

Applicable branches:
9.3

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution failure in /tmp/junit17532607815334754255 with arguments [myTask, -Dos.name=Linux, -Dos.version=6.14.0-1015-gcp, -i, --full-stacktrace, -Dtest.external=true, -I, /tmp/junit17532607815334754255/repositories-init.gradle, -Dtest.external=true]

Output:
The client will now receive all logging from the daemon (pid: 9463). The daemon log file: /dev/shm/bk/bk-agent-prod-gcp-1770319490480477328/elastic/elasticsearch-intake/build-tools/build/tmp/integTest/work/.gradle-test-kit/test-kit-daemon/9.3.1/daemon-9463.out.log
Starting 14th build in daemon [uptime: 1 mins 33.983 secs, performance: 99%, GC rate: 0.00/s, heap usage: 0% of 512 MiB, non-heap usage: 26% of 384 MiB]
Using 32 worker leases.
Operational build model parameters: {requiresToolingModels=false, parallelProjectExecution=false, configureOnDemand=false, configurationCache=false, configurationCacheParallelStore=false, configurationCacheParallelLoad=true, isolat
[truncated]

Issue Reasons:

  • [9.3] 4 consecutive failures in test override jdk usage via ES_JAVA_HOME for known jdk os incompatibilities
  • [9.3] 4 consecutive failures in step part1
  • [9.3] 2 consecutive failures in step part-1
  • [9.3] 4 consecutive failures in pipeline elasticsearch-intake
  • [9.3] 8 failures in test override jdk usage via ES_JAVA_HOME for known jdk os incompatibilities (80.0% fail rate in 10 executions)
  • [9.3] 4 failures in step part1 (100.0% fail rate in 4 executions)
  • [9.3] 4 failures in step part-1 (66.7% fail rate in 6 executions)
  • [9.3] 4 failures in pipeline elasticsearch-intake (100.0% fail rate in 4 executions)
  • [9.3] 3 failures in pipeline elasticsearch-pull-request (75.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

Metadata

Metadata

Assignees

Labels

:Delivery/BuildBuild or test infrastructure>test-failureTriaged test failures from CITeam:DeliveryMeta label for Delivery teamlow-riskAn open issue or test failure that is a low risk to future releases

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions