jitrolling build is broken

[kunalspathak]

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.

{
  "ErrorMessage": "",
  "BuildRetry": false
}

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[ghost]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak
See info in area-owners.md if you want to be subscribed.

Issue Details

---

jit rolling build is broken with error message of "upgrade pip to latest".

Author:	kunalspathak
Assignees:	-
Labels:	area-CodeGen-coreclr, untriaged
Milestone:	-

[kunalspathak]

@BruceForstall

[BruceForstall]

/__w/_temp/48445184-fd1b-4720-8069-2f03978e0806.sh: line 1: pip3: command not found
##[error]Bash exited with code '127'.

"Initialize job" shows:

Image: build.ubuntu.1804.amd64
Image Version: 2023.0216.171105

Maybe someone removed pip3 from the Docker container?

[BruceForstall]

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?

[ghost]

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

---

jit rolling build is broken with error message of "upgrade pip to latest".

Author:	kunalspathak
Assignees:	BruceForstall
Labels:	area-Infrastructure-coreclr
Milestone:	-

[BruceForstall]

This is an "internal" pipeline: https://dev.azure.com/dnceng/internal/_build?definitionId=902&_a=summary

[BruceForstall]

This is due to #84148

[EgorBo]

Since dotnet/dotnet-buildtools-prereqs-docker#847 is merged, are we waiting for some "update dependencies" PR now?

[BruceForstall]

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.

[sbomer]

Updating to the new images in #84863.

[BruceForstall]

This is now fixed. I manually triggered a rolling run after the fix in #84863 was mirrored and it worked.