Skip to content
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

Closed
kunalspathak opened this issue Apr 14, 2023 · 11 comments
Closed

jitrolling build is broken #84822

kunalspathak opened this issue Apr 14, 2023 · 11 comments
Assignees
Labels
area-Infrastructure-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Milestone

Comments

@kunalspathak
Copy link
Member

kunalspathak commented Apr 14, 2023

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 ghost added the untriaged New issue has not been triaged by the area owner label Apr 14, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Apr 14, 2023
@ghost
Copy link

ghost commented Apr 14, 2023

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
Copy link
Member Author

@BruceForstall

@BruceForstall
Copy link
Member

/__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
Copy link
Member

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?

@BruceForstall BruceForstall added area-Infrastructure-coreclr and removed area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI untriaged New issue has not been triaged by the area owner labels Apr 14, 2023
@BruceForstall BruceForstall added this to the 8.0.0 milestone Apr 14, 2023
@ghost
Copy link

ghost commented Apr 14, 2023

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 BruceForstall added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Apr 14, 2023
@BruceForstall
Copy link
Member

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

@BruceForstall
Copy link
Member

This is due to #84148

@EgorBo
Copy link
Member

EgorBo commented Apr 14, 2023

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

@BruceForstall
Copy link
Member

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
Copy link
Member

sbomer commented Apr 14, 2023

Updating to the new images in #84863.

@BruceForstall
Copy link
Member

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

@ghost ghost locked as resolved and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Projects
None yet
Development

No branches or pull requests

4 participants