You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDK content test, when running in the Alpine build leg for 7.0, ends up comparing the linux-x64 version of the MS SDK tarball instead of the linux-musl-x64 version. This is not an accurate test. Since it's Alpine, it should be checking the content of the linux-musl-x64 version to ensure that content matches correctly.
This happens because the PortableRid MSBuild property is set to linux-x64 when it should be set to `linux-musl-x64. This is set correctly in the 6.0 branch:
This was discovered while testing the changes in dotnet/installer#13074. Because PortableRid is set correctly there, it ends up using the linux-musl-x64 version of the tarball and exposed another unrelated issue.
8.0 does not currently include an alpine leg for the SDK content tests. However, the regex pattern for downloading the MSFT sdk matches that of 7.0 (i.e. uses linux instead of linux*). Therefore, in order to address #3715, this pattern will have to change to be linux*.
The SDK content test, when running in the Alpine build leg for 7.0, ends up comparing the
linux-x64
version of the MS SDK tarball instead of thelinux-musl-x64
version. This is not an accurate test. Since it's Alpine, it should be checking the content of thelinux-musl-x64
version to ensure that content matches correctly.This happens because the
PortableRid
MSBuild property is set tolinux-x64
when it should be set to `linux-musl-x64. This is set correctly in the 6.0 branch:https://github.com/dotnet/installer/blob/1b5e0e204956294804c290739a41e440d184d0af/src/SourceBuild/tarball/content/Directory.Build.props#L184
This was discovered while testing the changes in dotnet/installer#13074. Because
PortableRid
is set correctly there, it ends up using thelinux-musl-x64
version of the tarball and exposed another unrelated issue.Related to dotnet/installer#17324.
The text was updated successfully, but these errors were encountered: