-
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
Share init-compiler with arcade #59018
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Detailsnull
|
aa0eda8
to
6474682
Compare
6474682
to
b5e3e93
Compare
Failures are unrelated. |
@MattGal is the deprovisioning of the `"CoreCLR Product Build OSX arm64 release" leg the slow macOS machine issue? https://dev.azure.com/dnceng/public/_build/results?buildId=1358353&view=logs&jobId=a3584aa7-f6a0-5e90-05ca-4edce1db7c76&j=eb4db7b6-55d4-5d5f-e2fd-7706dfacdc48 |
I don't think so, this is just the previous MacOS problem where sometimes the machine management has a bad day. Anywhere you see cloning take a normal-ish amount of time and |
Thanks that matches my assumption. Do we have an open IcM for the deprovisioning issue? I remember that this issue plagued us in the past and as I have been seeing a few legs failing in the last two weeks but not any in the last months I wonder if this regressed again? |
The problem never went away, and will always exist. These are real macOS machines running in VMs on real physical hardware that occasionally loses its connection. The problem just dropped to a percentage low enough that we stopped opening IcMs about it (by your own description, 1.5 times per week doesn't sound like much). If you feel this is important enough to bring up with the Mac Cloud team (I've forwarded this along to some folks from the team via email), reach out on the First responders channel with some examples and we can start the conversation. |
@jkoritzinsky, could you merge this? causing conflict with arcade PR. |
Upstream PR: dotnet/arcade#7886.