-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
jitrolling build is broken #84822
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue Detailsjit rolling build is broken with error message of "upgrade pip to latest".
|
"Initialize job" shows:
Maybe someone removed pip3 from the Docker container? |
It looks like we switched from building with: mcr.microsoft.com/dotnet-buildtools/prereqs:centos-7 to building with: mcr.microsoft.com/dotnet-buildtools/prereqs:cbl-mariner-2.0-cross-amd64-20230410173854-2288685 And this obviously doesn't have the same packages installed. @sbomer @jkoritzinsky @steveisok It looks like you've all been actively making changes to the mariner Docker container definition in https://github.com/dotnet/dotnet-buildtools-prereqs-docker. Can you fix this? |
Tagging subscribers to this area: @hoyosjs Issue Detailsjit rolling build is broken with error message of "upgrade pip to latest".
|
This is an "internal" pipeline: https://dev.azure.com/dnceng/internal/_build?definitionId=902&_a=summary |
This is due to #84148 |
Since dotnet/dotnet-buildtools-prereqs-docker#847 is merged, are we waiting for some "update dependencies" PR now? |
My understanding is we need to wait for an official build of the docker images (https://dev.azure.com/dnceng/internal/_build?definitionId=1004 ?) and then a dotnet/runtime PR to update our YML to use the new images. |
Updating to the new images in #84863. |
This is now fixed. I manually triggered a rolling run after the fix in #84863 was mirrored and it worked. |
jit rolling build is broken with error message of "upgrade pip to latest".
Known Issue Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: