Skip to content
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

Closed
am11 opened this issue Jan 3, 2023 · 1 comment · Fixed by #80154
Closed

Wrong crossgen2 binary in artifacts/tests #80110

am11 opened this issue Jan 3, 2023 · 1 comment · Fixed by #80154
Labels
area-Infrastructure-coreclr in-pr There is an active PR which will close this issue when it is merged

Comments

@am11
Copy link
Member

am11 commented Jan 3, 2023

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'd crossgen2 executable under tools/ directory.

With build clr+libs followed by src/tests/build, the non-published (non-AOT, non-SingleFile) variant is copied at artifacts/tests/coreclr/<rid>.<configuration>/Tests/Core_Root/crossgen2/crossgen2 which we use in test runs.

With build clr+libs+packs followed by src/tests/build, both non-published and published variants are copied in artifacts/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 if packs 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)
  • test runner and places like R2RTest tool which are spawning dotnet crossgen2.dll or corerun crossgen2.dll to spawn crossgen2 executable instead
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jan 3, 2023
@ghost
Copy link

ghost commented Jan 3, 2023

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

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'd crossgen2 executable under tools/ directory.

With build clr+libs followed by src/tests/build, the non-published (non-AOT, non-SingleFile) variant is copied at artifacts/tests/coreclr/<rid>.<configuration>/Tests/Core_Root/crossgen2/crossgen2 which we use in test runs.

With build clr+libs+packs followed by src/tests/build, both non-published and published variants are copied in artifacts/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 if packs 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)
  • test runner and places like R2RTest tool which are spawning dotnet crossgen2.dll or corerun crossgen2.dll to spawn crossgen2 executable instead
Author: am11
Assignees: -
Labels:

area-Infrastructure-coreclr

Milestone: -

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 3, 2023
@am11 am11 removed the untriaged New issue has not been triaged by the area owner label Jan 4, 2023
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Feb 5, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Sep 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr in-pr There is an active PR which will close this issue when it is merged
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant