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] WindowsServiceTests test30StartStop failing #113160

Open
elasticsearchmachine opened this issue Sep 19, 2024 · 4 comments
Open

[CI] WindowsServiceTests test30StartStop failing #113160

elasticsearchmachine opened this issue Sep 19, 2024 · 4 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

Build Scans:

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: null

Issue Reasons:

  • [main] 5 failures in test test30StartStop (4.3% fail rate in 115 executions)
  • [main] 4 failures in step windows-2019_default-windows-archive_packaging-tests-windows-sample (4.0% fail rate in 99 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (3.0% fail rate in 100 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 Sep 19, 2024
elasticsearchmachine added a commit that referenced this issue Sep 19, 2024
@elasticsearchmachine
Mute org.elasticsearch.packaging.test.WindowsServiceTests test30Start…
4af30db 
…Stop #113160
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 5 failures in test test30StartStop (4.3% fail rate in 115 executions)
  • [main] 4 failures in step windows-2019_default-windows-archive_packaging-tests-windows-sample (4.0% fail rate in 99 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (3.0% fail rate in 100 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Sep 19, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@masseyke
Copy link
Member

I just muted this on the 8.x branch as well.

@mark-vieira
Copy link
Contributor

The error message here is very unhelpful. @rjernst @thecoop is this related to #113177 you think?

@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 Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
4 participants
@breskeby @masseyke @mark-vieira @elasticsearchmachine