Closed elasticsearchmachine closed 3 months ago
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 https://github.com/elastic/elasticsearch/pull/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 assertBusy
to sort this out.
This has been muted on branch main
Mute Reasons:
Build Scans:
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.
@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.
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?
Was the unmute and the fix in separate PRs?
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&_a=(controlGroupInput:(chainingSystem:HIERARCHICAL,controlStyle:twoLine,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!t),panels:('0c0c9cb8-ccd2-45c6-9b13-96bac4abc542':(explicitInput:(dataViewId:fbbdc689-be23-4b3d-8057-aa402e9ed0c5,enhancements:(),fieldName:task.keyword,grow:!t,id:'0c0c9cb8-ccd2-45c6-9b13-96bac4abc542',searchTechnique:wildcard,selectedOptions:!(),singleSelect:!t,title:'Gradle%20Task',width:medium),grow:!t,order:0,type:optionsListControl,width:small),'144933da-5c1b-4257-a969-7f43455a7901':(explicitInput:(dataViewId:fbbdc689-be23-4b3d-8057-aa402e9ed0c5,enhancements:(),fieldName:name.keyword,grow:!t,id:'144933da-5c1b-4257-a969-7f43455a7901',searchTechnique:wildcard,selectedOptions:!('test600Interrupt'),title:Test,width:medium),grow:!t,order:2,type:optionsListControl,width:medium),'4e6ad9d6-6fdc-4fcc-bf1a-aa6ca79e0850':(explicitInput:(dataViewId:fbbdc689-be23-4b3d-8057-aa402e9ed0c5,enhancements:(),fieldName:className.keyword,grow:!t,id:'4e6ad9d6-6fdc-4fcc-bf1a-aa6ca79e0850',searchTechnique:wildcard,selectedOptions:!('org.elasticsearch.packaging.test.DockerTests'),title:Suite,width:medium),grow:!t,order:1,type:optionsListControl,width:medium)))))
Failure Message:
Issue Reasons:
Note: This issue was created using new test triage automation. Please report issues or feedback to es-delivery.