-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] DockerTests test600Interrupt failing #111132
Comments
Pinging @elastic/es-delivery (Team:Delivery) |
Seems this is failing only on 7.17 because it's muted on the other branches. I've opened #111165 to unmute and observe. My suspicion is this is just a race condition where we send a sigkill and then ask for container logs and the shutdown hook simply hasn't fired yet. Might be as simple as an |
Investigating #111132 and it seems this test has been muted on `main` for some time. Let's unmute, to see if this is specific to the 7.17 branch or not.
Investigating elastic#111132 and it seems this test has been muted on `main` for some time. Let's unmute, to see if this is specific to the 7.17 branch or not.
Investigating elastic#111132 and it seems this test has been muted on `main` for some time. Let's unmute, to see if this is specific to the 7.17 branch or not.
This has been muted on branch main Mute Reasons:
Build Scans: |
Investigating elastic#111132 and it seems this test has been muted on `main` for some time. Let's unmute, to see if this is specific to the 7.17 branch or not.
Wrap check for container shutdown log message in an `assertBusy()` to deal with race conditions. Closes elastic#111132 # Conflicts: # muted-tests.yml
Wrap check for container shutdown log message in an `assertBusy()` to deal with race conditions. Closes elastic#111132 # Conflicts: # muted-tests.yml
Wrap check for container shutdown log message in an `assertBusy()` to deal with race conditions. Closes elastic#111132 # Conflicts: # muted-tests.yml # qa/os/src/test/java/org/elasticsearch/packaging/test/DockerTests.java
Wrap check for container shutdown log message in an `assertBusy()` to deal with race conditions. Closes elastic#111132 # Conflicts: # muted-tests.yml
This has been muted on branch 8.15 Mute Reasons:
Build Scans:
|
@brianseeders I thought that the automation wouldn't remute a test within 24 hours of an issue being closed? The above failures don't include the fix. |
Unmuted and closing this again. |
At the moment, it won't mute a test twice in 24h, or open a new issue if one has been closed in the last 24h. The muting doesn't look at recent issues. Was the unmute and the fix in separate PRs? How did the test run and fail without having the fix? Generally, this scenario shouldn't happen, because the unmute and the fix would be in the same PR? |
Yes. It was first unmuted and then a fix was backported. So perhaps this is an atypical scenario. |
Build Scans:
Reproduction Line:
Applicable branches:
8.15
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: