-
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
Enable Alpine ARM support #41982
Enable Alpine ARM support #41982
Conversation
This change enables Alpine ARM support in the lab build scripts, packages and RID graph
Tagging subscribers to this area: @ViktorHofer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good. However this is not adding any builds to either official builds or PR/CI.
@safern I have not realized this before, but @trylek mentioned it yesterday too. I am going to update this PR with changes in the runtime.yml (I hope I understand it correctly that that is where we define what gets built in official builds and PR/CI). But I am quite confused by the seemingly random selection of OSes / architectures for various templates in that file. Do you have a guidance on where it would make sense to add the Linux_musl_arm? I've started by trying to put it everywhere where I've seen Linux_musl_arm64, but I am not sure if that's the right approach. |
In |
Thanks @safern, I've just added a new commit that updates runtime.yml and runtime-official.yml. |
runtime/eng/pipelines/runtime.yml Line 911 in 8972613
|
Also, do we know what kind of test coverage we need for |
Ah, I've missed that one. I'll add it in a second. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from the yml changes.
@safern I can see that coreclr, libraries and installer builds for arm musl have succeeded, but library tests are failing early with this error:
Do you have any idea what can be wrong? Is it possible that it is some kind of chicken and egg issue? |
@janvorli - I think we should take a closer look at this bit:
|
Could it be that the dotnet host doesn't have support for Linux_musl_arm leg yet? We consume the host package produced from dotnet/runtime. So what we should probably do is merge this without running tests and then once we produce a new host package with musl_arm support update the package version and add test runs. |
I don't know where it was supposed to get the dotnet executable from. I was thinking that it would come from the installer build and test leg. But I guess you are most likely right and the package needs to be produced first. |
Yeah it comes from a Package, we don't yet use the live built host. We have an active issue to do that. |
Ok, let me disable the tests for now. |
@ericstj do the RID related changes look good to you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
This reverts commit d992e0c.
This change ports to release/5.0 enabling Alpine ARM support in the lab build scripts packages and RID graph. It enables CI and official builds.
This change enables Alpine ARM support in the lab build scripts,
packages and RID graph.