Update CI images to Azure Linux 4.0 - #134049
Conversation
|
Azure Pipelines: Successfully started running 6 pipeline(s). 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
|
Blocked on dotnet/dotnet-buildtools-prereqs-docker#1746. |
|
All configs are passing now. win-86 System.Buffer test failure is unrelated to the unix-only change. |
|
there are some more references in eng/pipelines/libraries/helix-queues-setup.yml but I assume we want to keep them (for now?) since they're actually testing on AZL3 not just build. I'll trigger a couple optional pipelines to be sure but overall LGTM |
|
/azp run runtime-community,runtime-sanitized,runtime-linuxbionic |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
That's right, we have azl3 and 4 coverage in those places. Perhaps we should just delete azl3 as usually we add "test coverage" for platform with high usage like Debian, Fedora etc. which I think azl3 does not qualify? |
|
Failures are unrelated. @jkoritzinsky, AddressSanitizer failure: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-134049-merge-d36df7f4c4a24199a6/nativeaot/1/console.dfa9ed91.log?helixlogtype=result |
|
/ba-g runtime-sanitized failures already exist on main and runtime ones are unrelated |
This is moslty to cover our internal usages which won't move to AZL4 for some time so keeping AZL3 testing is fine. |
|
we should do the same for the VMR |
|
See dotnet/dotnet-buildtools-prereqs-docker#1646.