-
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
Wrong crossgen2 binary in artifacts/tests #80110
Comments
Tagging subscribers to this area: @hoyosjs Issue DetailsProblemThe crossgen2 binary shipped in DetailsWe publish crossgen2 as a NativeAOT app on AOT supported platforms and as a SingleFile app on $other platforms. e.g. With With Proposed changes
|
Problem
The crossgen2 binary shipped in
microsoft.netcore.app.crossgen2
nuget package is not the binary we are testing in CI.Details
We publish crossgen2 as a NativeAOT app on AOT supported platforms and as a SingleFile app on $other platforms.
e.g.
microsoft.netcore.app.crossgen2.osx-arm64
nuget package v8.0.0-alpha.1.22605.1 has AOT'dcrossgen2
executable undertools/
directory.With
build clr+libs
followed bysrc/tests/build
, the non-published (non-AOT, non-SingleFile) variant is copied atartifacts/tests/coreclr/<rid>.<configuration>/Tests/Core_Root/crossgen2/crossgen2
which we use in test runs.With
build clr+libs+packs
followed bysrc/tests/build
, both non-published and published variants are copied inartifacts/tests/coreclr/<rid>.<configuration>/Tests/Core_Root/crossgen2
(non-published at./crossgen2
and published at./publish/<rid>/crossgen2
) and we still use non-published variant during the test runs.Proposed changes
src/tests/build
to always copy published variant of CG2 to artifacts (and publish it anyway ifpacks
subset wasn't built):artifacts/bin/coreclr/<rid>.<configuration>/crossgen2/<rid>/publish/*.*
->artifacts/tests/coreclr/<rid>.<configuration>/Tests/Core_Root/crossgen2/
(no need to copy non-published variant)dotnet crossgen2.dll
orcorerun crossgen2.dll
to spawncrossgen2
executable insteadThe text was updated successfully, but these errors were encountered: