The check "runtime (Build browser wasm li...) was stuck for 2 days with blank error message.

[cshung]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=624502

Build leg reported

Build / browser-wasm linux Release LibraryTests

Pull Request

dotnet/runtime#98712

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

I am not sure what can I do with a blank error message, so I just left the "Known issue core information" blank.

Force pushing a squashed version doesn't change anything, it is still stuck.

As the error in the build says: https://dev.azure.com/dnceng-public/public/_build/results?buildId=624502&view=logs&j=d4e38924-13a0-58bd-9074-6a4810543e7c this is due to a disconnect by the agent, which didn't leave an error message. I would attempt to rerun the leg. IF this is consistent for your PR, consider investigating whether your tests are causing an agent disconnect.

I don't think build analysis could've done much more here. The error in Azure devops is literally that there was no message, so build analysis presents as blank.

I'm closing this issue as it's not actionable by us and it won't make for a very good known issue with a blank message.

[cshung]

@riarenas It is still stuck on rerun by clicking the rerun button, it is stuck there after reporting "Received request to deprovision: The request was cancelled by the remote provider." again.

Last week I tried to push some other changes there and that doesn't change a thing either.

I would work with your repository's engineering team to figure out what you need to do to rerun this leg of your PR.

[cshung]

I would work with your repository's engineering team to figure out what you need to do to rerun this leg of your PR.

Who would be a good person to talk to for dotnet/runtime?

Basically, without an actual error, we cannot use a known issue for this.

It looks like your latest attempts are timing out, or causing agent disconnects during the build step.

@dotnet/runtime-infrastructure might be able to help.

[cshung]

@dotnet/runtime-infrastructure might be able to help.

Thank you!

[sbomer]

Looks like the same failure mode as dotnet/runtime#100424