You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"ErrorMessage": "['WasmTestOnChrome-MT-System.Net.Http.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=768825 Error message validated:[['WasmTestOnChrome-MT-System.Net.Http.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 8/7/2024 8:32:08 PM UTC
Unable to reproduce the issue locally, and it appears to have occurred only once on CI.
I'll close this for now, but if it happens again, I will reopen it.
...
[EXECUTION TIMED OUT]
Exit Code:-3Executor timed out after 1800 seconds and was killed
['WasmTestOnChrome-MT-System.Net.Http.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]
Activity
dotnet-policy-service commentedon Aug 7, 2024
Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
mkhamoyan commentedon Aug 12, 2024
Unable to reproduce the issue locally, and it appears to have occurred only once on CI.
I'll close this for now, but if it happens again, I will reopen it.
AaronRobinsonMSFT commentedon Nov 27, 2024
Seems to have occurred in #110211.
Log - https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-110211-merge-6ddd682c6df145b6b8/WasmTestOnChrome-MT-System.Net.Http.Functional.Tests/1/console.33e5096d.log?helixlogtype=result
jeffschwMSFT commentedon Mar 28, 2025
removing blocking-clean-ci as it has not failed in 30 days