-
Notifications
You must be signed in to change notification settings - Fork 4.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
increase timeout for websocket compression tests #52086
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRelates to #52031 This test is failing all the time. In such a situation we should disable or fix it immediately. I don't know why it is timing out, but we should be able to quickly see if it is indeed hanging rather than just slow.
|
/azp help |
This comment has been minimized.
This comment has been minimized.
/azp list |
This comment has been minimized.
This comment has been minimized.
I made it 30 seconds for everything as it's not quite only ARM. Also, it should never make a passing test any slower. TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
| where Finished >= datetime(2021-3-1 0:00:00)
//and Type == "System.Net.WebSockets.Tests.WebSocketDeflateTests"
and Method == "PayloadShouldHaveSimilarSizeWhenSplitIntoSegments"
//and Result == 'Fail'
//and QueueName1 contains "arm"
| summarize count() by Result, QueueAlias, Arguments, Message //, bin(Duration, 1)
|
I notice in the above table that it's always window bits 14 or 15, and (judging by the identical numbers) when it fails for one it always fails for the other. I also now notice that @CarnaViire already pointed this out :) I will update this to skip 14 and 15 while this is investigated. |
I also should have filtered out PR validation: TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
| where Finished >= datetime(2021-3-1 0:00:00)
and Type == "System.Net.WebSockets.Tests.WebSocketDeflateTests"
and Branch == "refs/heads/main"
| summarize count() by Method, Result, QueueAlias, Arguments, Message //, bin(Duration, 1)
|
The Android failures above show that resources were not loaded. That's clearly unrelated and no doubt we'll see it again if it's not fixed. |
Relates to #52031
This test is failing all the time. In such a situation we should disable or fix it immediately.
I don't know why it is timing out, but we should be able to quickly see if it is indeed hanging rather than just slow.