Ilona Tomkowicz
Ilona Tomkowicz
After consultation with @thaystg, I will block them.
> removing blocking-clean-ci due to not failing for 30 days FYI: It's because the test is disabled for more than 30 days, not fixed.
Most probably the fact that we used to reject all the attempts to receive when the socket was closed and now we keep letting the receive request to pass as...
Same story with NodeJS App Service. While the quoted docs say `allow outbound access from the webapp to oryx-cdn.microsoft.io on port 443`: 1) why is it not allowed by default...
No failures after the fix: https://github.com/dotnet/xharness/pull/1231.
All `LibraryTests_HybridGlobalization` on firefox fail because of it. > Yeah looks like we'd need a way to specify either --shm-size. The link you pasted gives the answer, docker's client run...
https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines/pullrequest/40290
It is not caught because `runtime-wasm` is excluded from `Build Analysis` step and the failures happen on ` runtime-wasm (Build browser-wasm windows Release LibraryTests_HybridGlobalization)` e.g. [log](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-103706-merge-1443fe9433bc46e6bb/WasmTestOnFirefox-ST-Common.Tests/1/console.4f431349.log?helixlogtype=result) ``` Console log: 'WasmTestOnFirefox-ST-Common.Tests'...
Waiting for the results of tests after the changes get propagated: https://github.com/dotnet/runtime/pull/104017
Not hit for a week since enabling while previously it had a frequency of hundreds of hits per week.