-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
microsoft.extensions.logging.generators.roslyn4.0.tests work item #72836
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'os-tvos': @steveisok, @akoeplinger Issue DetailsBuild terminating in CI with little indication why on TvOS: [195/201] xunit.core.dll -> xunit.core.dll.s, xunit.core.dll-llvm.o, xunit.core.aotdata
Runfo Creating Tracking Issue (data being generated)
|
The issue is the test suite untrimmed will generate an app size around 1GB. For whatever reason, the helix machines churn when trying to build it and end up timing out. The solution I think will work is to bring over the aggressive trimming test targets that exist in runtime/eng/testing/tests.mobile.targets Lines 179 to 217 in 73374e8
That will bring the app size down to about 300MB, which the helix machines should be able to handle without much trouble. Until the targets and xml descriptor files are sent over, the tests should be skipped. |
System.Text.RegularExpressions, Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests, and STJ source generator tests take too long to build on helix and time out before any tests are run. This is due in part to the amount of aot'd code, which ends up ballooning the app size to around 1GB. The solution is to enable aggressive trimming targets that are in tests.mobile.targets as this will shrink the app size considerably. Skipping these tests for now. Addresses dotnet#72834 Addresses dotnet#72836
Tagging subscribers to this area: @dotnet/area-extensions-logging Issue DetailsBuild terminating in CI with little indication why on TvOS:
Runfo Creating Tracking Issue (data being generated)
|
Do we really need to run source generator tests on tvOS and MacCatalyst? |
Maybe? I don't know if it has value or not. |
IMHO - I believe it has very little value. I don't think we are running msbuild, sdk, roslyn, nuget, etc. tests on mobile form factors. |
I agree, I don't see the value unless it's helpful to stress the system in general. |
System.Text.RegularExpressions, Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests, and STJ source generator tests take too long to build on helix and time out before any tests are run. This is due in part to the amount of aot'd code, which ends up ballooning the app size to around 1GB. The solution is to enable aggressive trimming targets that are in tests.mobile.targets as this will shrink the app size considerably. Skipping these tests for now. Addresses #72834 Addresses #72836
Since the test is disabled and we don't think running it makes sense, I'm going to close the issue. |
Build terminating in CI with little indication why on TvOS:
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-03666e5d9e604c64bd/Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests/1/console.c361ca0f.log?%3Fhelixlogtype%3Dresult
Runfo Tracking Issue: microsoft.extensions.logging.generators.roslyn4.0.tests work item
Build Result Summary
The text was updated successfully, but these errors were encountered: