-
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
Runtime Tests Linux_musl arm fails with "The "FindDotNetCliPackage" task failed unexpectedly." #44541
Comments
Turning this into a tracking issue. It seems to only affect linux-musl-arm outerloop pipelines, but there's 106 hits over 7 days, so it seems somewhat deterministic. |
Hmm, that's weird. @janvorli, it looks like we're actually running the linux_musl arm tests in outerloop runs only, not in PR / CI runs. Did you try to run the outerloop pipeline when introducing the leg i.o.w. do we know if this ever worked? |
It seems like it is trying to download it from: https://dotnetcli.azureedge.net/dotnet/Runtime/5.0.0-rc.2.20475.5/dotnet-runtime-5.0.0-rc.2.20475.5-linux-musl-arm.tar.gz I wonder if we shipped a runtime for linux-musl-arm for that version of the runtime. |
We are running the libraries linux_musl_arm tests in the CI. I can see the leg in the recent CIs. It seems that run is executed only if coreclr was changed. |
Here is an example of a log from such a test run: |
This works: https://dotnetcli.azureedge.net/dotnet/Runtime/5.0.0/dotnet-runtime-5.0.0-linux-musl-arm.tar.gz It seems like we're using the BundledNetCoreAppVersion which is defined by the sdk used to build... in this case I suggest changing this:
5.0.0 in the meantime until we update our SDK to use 5.0.0 in our global.json
|
Btw, @janvorli, it seems like Alpine ARM is not included in the release notes for 5.0.0: https://github.com/dotnet/core/blob/master/release-notes/5.0/5.0.0/5.0.0.md#net-500---november-10-2020 |
@janvorli - I believe the log you mention corresponds to a "libraries" Linux_musl arm run, the run that's failing in the outerloop pipeline is a "coreclr" Linux_musl arm run; these two still use somewhat separate scripts and so the properties are likely forked, i.o.w. we should probably do what Santi suggests for the time being. |
That's what I said - we are running only the libraries tests in the CI. |
I see, sorry about missing that bit in your previous response. |
It is intentional, I have found only last week that the aspnetcore packages are not built for 5.0. I have thought I've seen 5.0-RC2 ones being produced after I've merged in my change to aspnetcore, but I've obviously made a mistake and seen something else. So we will fix that for 5.0.1. |
Sounds good. Didn't know if it was intentional or missed. Thanks for the update. |
Closing as not observable anymore. |
Full log:
An example:
https://dev.azure.com/dnceng/public/_build/results?buildId=882549&view=logs&j=22eeac8c-742e-5aad-c88c-3907a882a5f0&t=8e36944f-99e4-5f3f-4391-f6a5a224ec79
It looks like the last item that blocks at least some green runs after we disabled individual failing tests, should we disable the job?
Link #702
Runfo Tracking Issue: Linux Musl ARM Outerloop can't find dotnet cli package
Build Result Summary
The text was updated successfully, but these errors were encountered: