-
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
[iOS] Enable Diagnostics.Tracing tests #72545
Conversation
Fixes an issue where a test project that contains native libraries will fool the AOT compiler task in thinking there are assemblies in different locations. This causes .aotdata files to not be bundled with the test app and ends up causing a runtime assertion.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
@radical I'm not sure if switching the Filter / Ensure methods are going to impact you. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
I think it should be fine. |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
We can reenable these as well #56073 We probably also need to add |
Hm
|
Could you explain what exactly is happening here?
|
…assemblies `iOS` targets depend on these files being next to the original assemblies. But that assumption breaks when `MonoAOTCompiler` copies the assemblies to `aot-in` directory, and emits the `.aotdata` files there.
.. unmanaged assemblies. 1. Completely ignore unmanaged assemblies 2. Assemblies to be skipped for AOT, should still get copied to `aot-in` dir. If this is not done, then blazor apps would break because they skip` Microsoft.JSInterop.WebAssembly` but other assemblies depend on it, thus causing `mono-aot-cross` to fail because it can't find the JSInterop assembly.
I have pushed some changes that fixes the issue in two ways:
|
/azp run runtime-extra-platforms,runtime-wasm |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-extra-platforms,runtime-wasm |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
System.Diagnostics.Tracing tests pass on tvOS. The other failures are unrelated. |
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.
Looks good to me! If we can add new issues/reference existing ones for any new project/test skips that'd be good.
<!-- | ||
System.Formats.Cbor crashes on tvOS | ||
--> | ||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)System.Formats.Cbor\tests\System.Formats.Cbor.Tests.csproj" /> | ||
|
||
<!-- | ||
Test apps that are too large and take too long to build | ||
Keep here until aggressive trimming targets can work on helix. | ||
--> | ||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)System.Text.RegularExpressions\tests\UnitTests\System.Text.RegularExpressions.Tests.csproj" /> | ||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)System.Text.Json\tests\System.Text.Json.SourceGeneration.Tests\System.Text.Json.SourceGeneration.Roslyn4.0.Tests.csproj" /> | ||
|
||
|
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.
Are these new failures? Are there issues associated that we can put in the comments?
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.
If it's just links that we need to add, then we can do that in a follow up PR.
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.
There will be. I would rather address it in #67861
Fixes an issue where a test project that contains native libraries will fool the AOT compiler task in thinking there are assemblies in different locations. This causes .aotdata files to not be bundled with the test app and ends up causing a runtime assertion.
Fixes #51382