Uh oh!
There was an error while loading. Please reload this page.
Rev Alpine WithNode from 3.9 to 3.13 - #57324
Conversation
ghost
commented
Aug 12, 2021
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsUpdating to 3.14 now will buy us ~2 years before this latest version reaches EOL. Fixes #56672
|
am11
commented
Aug 12, 2021
jkotas
commented
Aug 12, 2021
According to https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md#linux, we want to support Alpine 3.13+ for .NET 6. Are binaries built on Alpine 3.14 going to run on Alpine 3.13? |
am11
commented
Aug 12, 2021
They should work (as time64 changes were included in 3.13). I will test it. |
am11
commented
Aug 12, 2021
Locally I was able to build the main branch without any changes: docker run -v $(pwd):/runtime \
-it mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.14-WithNode-20210812132848-d90babf \
/runtime/src/coreclr/build-runtime.sh checked x64but on CI it was failing to find python while it is clearly there, but when i worked around it, it is now failing with |
hoyosjs
commented
Aug 13, 2021
@am11 looks like the container doesn't have curl? (and maybe doing the volume mount masks this as you may have a |
am11
commented
Aug 13, 2021
hoyosjs
commented
Aug 13, 2021
I tried with copied IDs from the build logs and I was still able to get the SDK. |
am11
commented
Aug 14, 2021
Yes, the docker container |
ViktorHofer
commented
Aug 16, 2021
@am11 please let us know if we can help anyhow. |
@ViktorHofer, it is still a mystery to me as CI error is not reproducible locally. e.g. this leg https://dev.azure.com/dnceng/public/_build/results?buildId=1291489&view=logs&jobId=0e64859c-a870-5a74-6b6e-333fc1003298&j=0e64859c-a870-5a74-6b6e-333fc1003298&t=5da9eef6-c013-592b-ccae-2e46c52786d0 is apparently using container I just (temporarily) deleted runtime/src/coreclr/build-runtime.sh Lines 55 to 58 in 6acb72b If we test it locally with same command used by this failing CI leg: it builds coreclr successfully. Do you see anything unusual from the logs that could be causing |
ViktorHofer
commented
Aug 16, 2021
I'll take a look. Let me also cc @safern and @jkoritzinsky |
ViktorHofer
commented
Aug 20, 2021
@hoyosjs@jkoritzinsky any other ideas? I'm currently a bit short on time, maybe you have some additional ideas? |
ViktorHofer
commented
Sep 1, 2021
@MattGal do you think you can help here? |
MattGal
commented
Sep 1, 2021
No guarantees but sure, I'll take a look |
MattGal
commented
Sep 1, 2021
@ViktorHofer I can't reproduce this running main build inside a |
|
MattGal
commented
Sep 1, 2021
Super weird but does seem to be noticed and known externally: dotnet/install-scripts#206. I'm running the same image you used to run the same CI build from a Windows box. I wonder if you started from an Ubuntu 18.04/20.04 if you could get a repro. |
hoyosjs
commented
Sep 1, 2021
I couldn't repro on a physical Ubuntu box with that container on top. |
MattGal
commented
Sep 1, 2021
Maybe just try |
am11
commented
Sep 1, 2021
Flakiness is really not the problem. On other systems, you can build using this new container reliably and in AzDO it is always failing to run build step inside the container (it is apparently running build step on host system rather than the container). Logs are not indicating any problem. |
37bf805 to
2888eafCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Also, * update helix queues from 3.12 to 3.13 * add 3.14 helix queues * update performance job to install cargo from main branch
174c287 to
7e1fb3eCompare| # Linux musl x64 | ||
| - ${{ if eq(parameters.platform, 'Linux_musl_x64') }}: | ||
| - ${{ if eq(parameters.jobParameters.isFullMatrix, false) }}: |
There was a problem hiding this comment.
can we test on 3.13 on fullMatrix == true? Meaning on rolling CI?
There was a problem hiding this comment.
Yup, didn't mean to press delete on rolling ones 🤣
It seems like you have a yaml syntax error 😢 : https://dev.azure.com/dnceng/public/_build/results?buildId=1384687&view=results |
aik-jahoda
commented
Sep 29, 2021
There is a JSON failure on Alpine.314.Arm64.Open. @safern do you think the failure is related to the change or we can merge this PR? |
danmoseley
commented
Sep 29, 2021
The JSON crash has a dump. We should look at that dump -- there is a how-to-debug-dump.md file there to help. The regex issue is known and fixed already. |
am11
commented
Sep 29, 2021
Isn't it #57198? |
safern
commented
Sep 29, 2021
I think we should at least look at the dump to make sure if it is: #57198 before merging something that could potentially introduce a failure to CI. |
am11
commented
Sep 29, 2021
The dump link on that issue is expired and Eirik had no success with Maybe rerun the job to see if the issue persist? |
safern
commented
Sep 29, 2021
Sounds good to me. |
am11
commented
Sep 29, 2021
danmoseley
commented
Sep 29, 2021
Ah gotcha. Is there anything that can be gotten out of this dump? |
am11
commented
Sep 29, 2021
I am working on it. 🙂 |
am11
commented
Sep 29, 2021
|
aik-jahoda
commented
Sep 30, 2021
Sounds like both test failures are known and tracked/fixed already. Can we merge this PR? |
Also,
Fixes#56672