Skip to content

[CI] NodeEnvironmentTests testGetBestDowngradeVersion failing #121316

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

Closed
elasticsearchmachine opened this issue Jan 30, 2025 · 6 comments · Fixed by #127646
Closed

[CI] NodeEnvironmentTests testGetBestDowngradeVersion failing #121316

elasticsearchmachine opened this issue Jan 30, 2025 · 6 comments · Fixed by #127646
Assignees
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 Jan 30, 2025

Build Scans:

Reproduction Line:

./gradlew ":server:test" --tests "org.elasticsearch.env.NodeEnvironmentTests.testGetBestDowngradeVersion" -Dtests.seed=3968A5F46FA01596 -Dtests.locale=mzn-IR -Dtests.timezone=America/Adak -Druntime.java=23

Applicable branches:
9.0

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <8.18.0>
     but: was <8.19.0>

Issue Reasons:

  • [9.0] 6 consecutive failures in test testGetBestDowngradeVersion
  • [9.0] 15 consecutive failures in step part1
  • [9.0] 6 consecutive failures in step part-1
  • [9.0] 2 consecutive failures in step checkpart1_release-tests
  • [9.0] 15 consecutive failures in pipeline elasticsearch-intake
  • [9.0] 6 consecutive failures in pipeline elasticsearch-pull-request
  • [9.0] 24 failures in test testGetBestDowngradeVersion (37.5% fail rate in 64 executions)
  • [9.0] 15 failures in step part1 (88.2% fail rate in 17 executions)
  • [9.0] 6 failures in step part-1 (85.7% fail rate in 7 executions)
  • [9.0] 2 failures in step checkpart1_release-tests (66.7% fail rate in 3 executions)
  • [9.0] 15 failures in pipeline elasticsearch-intake (88.2% fail rate in 17 executions)
  • [9.0] 6 failures in pipeline elasticsearch-pull-request (85.7% fail rate in 7 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 labels Jan 30, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 consecutive failures in test testGetBestDowngradeVersion
  • [main] 2 consecutive failures in step part-1
  • [main] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 4 failures in test testGetBestDowngradeVersion (1.6% fail rate in 246 executions)
  • [main] 2 failures in step part-1 (2.0% fail rate in 99 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.0% fail rate in 100 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 30, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

smalyshev pushed a commit to smalyshev/elasticsearch that referenced this issue Jan 30, 2025
@ldematte ldematte 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 Jan 31, 2025
@ldematte
Copy link
Contributor

I think the recent introduction of 8.19/the 8.19 branch may have broken some assumptions @alexey-ivanov-es
Can you take a look at these test to understand it this is just a test issue and needs a minor adjustment, or if this needs more reworking?

@thecoop
Copy link
Member

thecoop commented Jan 31, 2025

This is also broken on 9.0.

This is because assumptions based on min compat being 'last version of previous minor' do not apply for the planned 8.19 release, where 9.0 min compat will be 8.18. This is breaking tests around this

@thecoop
Copy link
Member

thecoop commented Jan 31, 2025

#121394 mutes it on 9.0 too

@thecoop thecoop added the :Delivery/Tooling Developer tooliing and automation label Jan 31, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Delivery Meta label for Delivery team label Jan 31, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@prdoyle prdoyle self-assigned this May 2, 2025
@prdoyle prdoyle removed Team:Delivery Meta label for Delivery team :Delivery/Tooling Developer tooliing and automation labels May 2, 2025
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

Successfully merging a pull request may close this issue.

4 participants