Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CI] LegacyYamlRestTestPluginFuncTest plugin projects are wired into test cluster setup failing #125261

Closed
elasticsearchmachine opened this issue Mar 19, 2025 · 2 comments
Closed

[CI] LegacyYamlRestTestPluginFuncTest plugin projects are wired into test cluster setup failing #125261

elasticsearchmachine opened this issue Mar 19, 2025 · 2 comments
Assignees
@breskeby
Labels
:Delivery/Build Build or test infrastructure low-risk An open issue or test failure that is a low risk to future releases Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 19, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

null

Applicable branches:
8.16

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.spockframework.runtime.ConditionFailedWithExceptionError: Condition failed with Exception:

result.task(":distribution:archives:integ-test-zip:buildExpanded").outcome == TaskOutcome.SUCCESS
|      |                                                           |
|      null                                                        java.lang.NullPointerException: Cannot get property 'outcome' on null object
|                                                                  	at org.elasticsearch.gradle.internal.test.rest.LegacyYamlRestTestPluginFuncTest.#type projects are wired into test cluster setup(LegacyYamlRestTestPluginFuncTest.groovy:143)
<org.elasticsearch.gradle.internal.test.NormalizeOutputGradleRunner$NormalizedBuildResult@7ca16adc delegate=org.gradle.testkit.runner.internal.FeatureCheckBuildResult@4ac8768e normalizedString=null this$0=org.elasticsearch.gradle.internal.test.NormalizeOutputGradleRunner@1e957e2f>

Issue Reasons:

  • [8.16] 4 consecutive failures in test plugin projects are wired into test cluster setup
  • [8.16] 5 consecutive failures in step almalinux-8-aarch64_checkpart1_platform-support-arm
  • [8.16] 5 consecutive failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm
  • [8.16] 6 consecutive failures in pipeline elasticsearch-periodic-platform-support
  • [8.16] 10 failures in test plugin projects are wired into test cluster setup (35.7% fail rate in 28 executions)
  • [8.16] 5 failures in step almalinux-8-aarch64_checkpart1_platform-support-arm (100.0% fail rate in 5 executions)
  • [8.16] 5 failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm (100.0% fail rate in 5 executions)
  • [8.16] 6 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 6 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 19, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-delivery (Team:Delivery)

@breskeby breskeby self-assigned this Mar 19, 2025
@breskeby breskeby added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 19, 2025
@breskeby
Copy link
Contributor

Addressed by #125467

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@breskeby breskeby

Labels
:Delivery/Build Build or test infrastructure low-risk An open issue or test failure that is a low risk to future releases Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@breskeby @elasticsearchmachine