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.

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

[CI] BuildParameterExtensionSpec getRuntimeJavaDetails is cached anc concurrently accessible failing #119234

Open
elasticsearchmachine opened this issue Dec 23, 2024 · 2 comments
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 Dec 23, 2024

Build Scans:

Reproduction Line:

null

Applicable branches:
8.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.spockframework.runtime.SpockComparisonFailure: Condition not satisfied:

futures.any { it.isCancelled() || it.isDone() == false } == false
|       |                                                |
|       true                                             false
[java.util.concurrent.FutureTask@3661b732[Completed normally], java.util.concurrent.FutureTask@5111f814[Completed normally], java.util.concurrent.FutureTask@71eafb64[Completed normally], java.util.concurrent.FutureTask@491cc0eb[Completed normally], java.util.concurrent.FutureTask@727f36dd[Completed normally], java.util.concurrent.FutureTask@2c70a1de[Completed normally], java.util.concurrent.FutureTask@ae74eef[Completed normally], java.util.concurrent.FutureTask@2553dcc0[Completed normally], java.util.concurrent.FutureTask@2e91cf69[Completed normally], java.util.concurrent.FutureTask@746e534[Completed normally]]

Issue Reasons:

  • [8.17] 3 consecutive failures in test getRuntimeJavaDetails is cached anc concurrently accessible
  • [8.17] 2 consecutive failures in step part1
  • [8.17] 2 consecutive failures in pipeline elasticsearch-intake
  • [8.17] 4 failures in test getRuntimeJavaDetails is cached anc concurrently accessible (14.3% fail rate in 28 executions)
  • [8.17] 3 failures in step part1 (60.0% fail rate in 5 executions)
  • [8.17] 3 failures in pipeline elasticsearch-intake (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.

@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Dec 23, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.17

Mute Reasons:

  • [8.17] 2 failures in test getRuntimeJavaDetails is cached anc concurrently accessible (7.7% fail rate in 26 executions)
  • [8.17] 2 failures in step part1 (50.0% fail rate in 4 executions)
  • [8.17] 2 failures in pipeline elasticsearch-intake (66.7% fail rate in 3 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Dec 23, 2024
…ec getRuntimeJavaDetails is cached anc concurrently accessible #119234
@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 23, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

breskeby added a commit to breskeby/elasticsearch that referenced this issue Dec 23, 2024
@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 Dec 23, 2024
breskeby added a commit to breskeby/elasticsearch that referenced this issue Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants