-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add missing startup flags in runtime/start event #55151
Conversation
At first I thought this might be a profiler error, but it looks like all the test logs indicate those passed. @davmason could you validate that? one said:
Looking at the Helix logs, I see some python errors:
@dotnet/runtime-infrastructure it looks like there were some permissions issues while pip was installing packages. Is this ignorable? I'm going to rerun the job and see if it happens again. |
cc @dotnet/dnceng |
The actual error here is not that warning, rather the Azure Devops test result API hanging up on us:
Please consider including correlation id with such comments, it saves time. |
I took a look, and it's not exactly what I thought, rather a network problem talking to pypi.org not AzDO. However, it's still a piece that is being re-written to be more reliable and should be phased out quite soon (like, next-promoted arcade dependency flow soon).
@ChadNedzlek 's changes to use the new built-in AzDO reporting are on their way, until then you'll need to retry when pypi has an outage (and perhaps updating your image to |
Add missing startup flags in Runtime/Start event.
This should fix #52042.
cc @josalem