Skip to content
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

Azure Pipeline Tests "failed" with HTTP request timeout #11071

Closed
Szpoti opened this issue Jul 19, 2023 · 3 comments · Fixed by #11255
Closed

Azure Pipeline Tests "failed" with HTTP request timeout #11071

Szpoti opened this issue Jul 19, 2023 · 3 comments · Fixed by #11255
Assignees

Comments

@Szpoti
Copy link
Contributor

Szpoti commented Jul 19, 2023

OSX run failed: https://github.com/zkSNACKs/WalletWasabi/runs/15165893562
Azure logs: https://dev.azure.com/zkSNACKs/Wasabi/_build/results?buildId=102354&view=logs&j=a5e52b91-c83f-5429-4a68-c246fc63a4f7&t=d4f393a6-5f7f-57b8-9785-cfc6593dde33

You can see in the logs that

Test Run Successful.
Total tests: 1087
     Passed: 1087
 Total time: 15.0790 Minutes

But when Azure tried to upload/publish the results

Async Command Start: Publish test results
Async Command End: Publish test results
##[error]The HTTP request timed out after 00:00:30.
Finishing: Test Debug

it got timed out, thus indicating that the tests have faild, even though they didn't.
image
You can see that everything else went smooth. Probably a one time thing on Azure's side, but can we do something that in this case, it should say that the tests were successfull anyway?

@Pule08
Copy link

Pule08 commented Jul 24, 2023

@kiminuo will be able to start working on that from next week (07.31->)

@kiminuo
Copy link
Contributor

kiminuo commented Aug 5, 2023

I have checked https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/dotnet-core-cli-v2?view=azure-pipelines#examples and I can't see anything that would really help us.

What seems to be useful is to check https://status.dev.azure.com/_history that mentions Azure incidents. And there was one but it's hard to know if it was really the issue or not.

I have also tried to filter out failing builds https://dev.azure.com/zkSNACKs/Wasabi/_build?definitionId=2&_a=summary&statusFilter=failed

My best guess is that it's an external issue that was only temporary. I'm not aware of any specific action we can take at the moment.

@molnard
Copy link
Contributor

molnard commented Aug 10, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants