-
Notifications
You must be signed in to change notification settings - Fork 352
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
install-native-dependencies.sh failing in CI #11740
Comments
@jkotas the error doesn't seem to be something that the engineering team owns. The issue should be opened in the runtime repo. Please let us know if you need help moving the issue |
I believe that the engineering team owns the installation of the native dependencies like python on the build machines. You can see number of issues about that in the arcade repo, e.g. #2673 . The specific script where this is failing is dotnet/runtime specific because we never achieved a grand unified way to install the native dependencies. There is not much that the engineers working on dotnet/runtime can do about installation of the native dependencies on the build machines. The solution for it has to be driven from the engineering team - for both secure supply chain aspects and reliability aspects. |
Fair points I see that your build failed in a Hosted OSX agent (which we don't own) and it passed on retry. I'll keep the issue open for today but I don't see much we can investigate/do here. Does it sound fair? |
I see some hits today, given that retrying the build helped yesterday. I'll turn on build retry for this known issue and keep it open for tracking |
Adding @jonfortescue and @Chrisboh who are likely interested in this from the native dependency / secure supply chain perspective as a good case in point where runtime has unique challenges. |
Ah, yeah, macOS was out of scope for my effort because we don't produce our own macOS build images. I don't have strong opinions one way or the other with this -- it's a tricky situation. |
@jkotas given that the script is failing to talk to a service we don't control, is it possible to add a retry to runtime's scripts? |
The script is talking to github.com. Notice that the first error is What is our usual retry policy for git commands? I have looked around in dotnet/runtime and I have not found any retry loops around git commands. |
@jkotas there's not a specific example to my knowledge, but generally we just do an exponential retry loop. |
As we have not seen additional instances of this for the last week, I am closing this issue. Feel free to re-open it should you experience this again. |
Build
https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=95035
Build leg reported
Build / CoreCLR Product Build OSX x64 checked / Install native dependencies
Pull Request
dotnet/runtime#78922
Action required for the engineering services team
To triage this issue (First Responder / @dotnet/dnceng):
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Report
Summary
Report
Summary
The text was updated successfully, but these errors were encountered: