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] TracesApmIT testApmIntegration failing #122129

Open
elasticsearchmachine opened this issue Feb 8, 2025 · 6 comments
Open

[CI] TracesApmIT testApmIntegration failing #122129

elasticsearchmachine opened this issue Feb 8, 2025 · 6 comments
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Feb 8, 2025

Build Scans:

Reproduction Line:

./gradlew ":test:external-modules:test-apm-integration:javaRestTest" --tests "org.elasticsearch.test.apmintegration.TracesApmIT.testApmIntegration" -Dtests.seed=70562D7B3B3B3228 -Dtests.locale=pa-Guru -Dtests.timezone=Antarctica/Rothera -Druntime.java=21 -Dtests.fips.enabled=true

Applicable branches:
9.0

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: State is not RESPONSE (REQUEST)

Issue Reasons:

  • [9.0] 4 failures in test testApmIntegration (0.7% fail rate in 567 executions)
  • [9.0] 3 failures in step part-1 (4.2% fail rate in 71 executions)
  • [9.0] 2 failures in pipeline elasticsearch-pull-request (2.8% fail rate in 71 executions)

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

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@jdconrad
Copy link
Contributor

jdconrad commented Feb 14, 2025

This is probably related to #109335 where the apm server isn't aware that the cluster is shutting down. There is probably a way to make this test more robust prior to converting to the OTEL SDK. This is low-risk for these reasons.

@jdconrad jdconrad 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 Feb 14, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testApmIntegration (1.2% fail rate in 170 executions)

Build Scans:

@ldematte
Copy link
Contributor

The PR failure (2nd here) is bogus, as it was related to adding Files instrumentation and the APM agent does some strange stuff. Fixed now. I wonder if we should unmute the test, or like @jdconrad says if we should make it more lenient before.

@alexey-ivanov-es
Copy link
Contributor

There is another muted APM test (muted after two failures, one of which occurred in the same PR): 123022. Since the failure in the PR was caused by an issue in the PR itself and there is only one failure outside the PR, I would just unmute them for now

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 9.0

Mute Reasons:

  • [9.0] 4 failures in test testApmIntegration (0.7% fail rate in 567 executions)
  • [9.0] 3 failures in step part-1 (4.2% fail rate in 71 executions)
  • [9.0] 2 failures in pipeline elasticsearch-pull-request (2.8% fail rate in 71 executions)

Build Scans:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants