Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 NativeAOT runtime tests on MacCatalyst #102882
Enable NativeAOT runtime tests on MacCatalyst #102882
Changes from all commits
34ae7e3
e856611
5d5f3b4
3fc991a
d05f567
a0861ae
b2c3e18
97c4e81
10cb545
21292b3
a26f16a
f66559f
0e28387
c7eb67f
6090f8b
01abe70
0ce9e02
8d8f9bd
9ec56c4
0329bd6
c3072fc
798a7c4
fdb4813
97159f3
b906a65
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Why do we need to set
/p:BuildNativeAOTRuntimePack=true
here, I thought the property is used only when building the runtime bits, not the tests?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.
I can't recall the initial reason for including it, and it is likely no longer needed since we now use a single build command. I believe it was related to the initial multi-command build process.
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.
Without this property jobs reports:
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.
Thanks for checking it out. I think we should investigate/refactor this (as a follow-up).
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.
Isn't
Contents
dir already contained in theBundleContent
? (I am not sure why we need to special-case maccatalyst)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.
It should be already there, but I couldn't recursively copy content in msbuild from the build directory to the bundle. The
RecursiveDir
metadata forBundleContent
is empty here. Please share any ideas on how to avoid "manual" copy.It is in place to verify E2E tests, but I think we need to resolve this before merging.
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.
Yes, that is what I was confused about.