-
Notifications
You must be signed in to change notification settings - Fork 272
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
ARM64 CI Leg fails due to missing python3 #333
Comments
Those issues seem fairly old - does anyone know why ARM64 went away? @ulisesh ? |
@billwert What do you mean? They are one day and 16 days old? |
The queue Ubuntu.1604.Arm64.Open was moved from running on bare-metal servers to run on containers. The docker images we are using don't include Python3 making Adam's jobs fail. We are working to add Python3 |
Malena is working on adding python3 to all of the queues (windows and linux), so when that work is in, we should be good. Because this is a machine configuration issues, I would suggest we disable the Arm64 runs until this work is in so that PRs aren't blocked (in particular the dependency update jobs) |
Until dotnet#333 is fixed we'll not try to run the ARM64 jobs so other runs can have clean checks.
@adiaaida good thinking. I was just working on this - check out #351. |
I believe the change has been checked in and all of the machines (all queues) should have python3 installed on them. |
@adiaaida thanks! I will try to re-enable the runs for ARM then |
@ulisesh @adiaaida The python3 is still missing on some machines, I tried to re-enable the ARM runs in #387 and failed:
|
It's not an issue anymore |
So far all the ARM64 machines had python3 installed, now they don't.
Related issues:
https://github.com/dotnet/core-eng/issues/5338
https://github.com/dotnet/core-eng/issues/5220
The text was updated successfully, but these errors were encountered: