Re-enable trimming of library tests on Apple mobile #104097
Conversation
|
/azp run runtime-extra-platforms |
|
Tagging subscribers to this area: @directhex, @matouskozak |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| @@ -39,8 +39,7 @@ jobs: | |||
| ${{ if eq(variables['isRollingBuild'], true) }}: | |||
| buildArgs: -s mono+libs+libs.tests -c $(_BuildConfig) /p:ArchiveTests=true /p:DevTeamProvisioning=- /p:RunAOTCompilation=true $(_runSmokeTestsOnlyArg) /p:BuildTestsOnHelix=true /p:EnableAdditionalTimezoneChecks=true /p:UsePortableRuntimePack=true /p:BuildDarwinFrameworks=true /p:IsManualOrRollingBuild=true /p:EnableAggressiveTrimming=false | |||
| ${{ else }}: | |||
| # Tracking issue: https://github.com/dotnet/runtime/issues/82637 | |||
| buildArgs: -s mono+libs+libs.tests -c $(_BuildConfig) /p:ArchiveTests=true /p:DevTeamProvisioning=- /p:RunAOTCompilation=true $(_runSmokeTestsOnlyArg) /p:BuildTestsOnHelix=true /p:EnableAdditionalTimezoneChecks=true /p:UsePortableRuntimePack=true /p:BuildDarwinFrameworks=true /p:IsManualOrRollingBuild=true /p:EnableAggressiveTrimming=false | |||
| buildArgs: -s mono+libs+libs.tests -c $(_BuildConfig) /p:ArchiveTests=true /p:DevTeamProvisioning=- /p:RunAOTCompilation=true $(_runSmokeTestsOnlyArg) /p:BuildTestsOnHelix=true /p:EnableAdditionalTimezoneChecks=true /p:UsePortableRuntimePack=true /p:BuildDarwinFrameworks=true /p:IsManualOrRollingBuild=true /p:EnableAggressiveTrimming=true | |||
There was a problem hiding this comment.
Since our iOS/tvOS builds are trimming on Helix by default, to prevent future hard-to-detect issues on CI, I would suggest that we add a trigger on changes in the tools_illink subset.
| @@ -1008,8 +1008,7 @@ extends: | |||
| jobParameters: | |||
| testGroup: innerloop | |||
| nameSuffix: AllSubsets_Mono | |||
| # Tracking issue: https://github.com/dotnet/runtime/issues/82637 | |||
| buildArgs: -s mono+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:DevTeamProvisioning=- /p:RunAOTCompilation=true /p:RunSmokeTestsOnly=true /p:BuildTestsOnHelix=true /p:EnableAdditionalTimezoneChecks=true /p:UsePortableRuntimePack=true /p:BuildDarwinFrameworks=true /p:EnableAggressiveTrimming=false | |||
| buildArgs: -s mono+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:DevTeamProvisioning=- /p:RunAOTCompilation=true /p:RunSmokeTestsOnly=true /p:BuildTestsOnHelix=true /p:EnableAdditionalTimezoneChecks=true /p:UsePortableRuntimePack=true /p:BuildDarwinFrameworks=true /p:EnableAggressiveTrimming=true | |||
| @@ -12,6 +12,8 @@ | |||
| <!-- Forced by ILLink targets --> | |||
| <SelfContained>true</SelfContained> | |||
| <PublishDir>$(OriginalPublishDir)</PublishDir> | |||
| <!-- Prevent getting DynamicCodeSupport=true default from ILLink targets that are imported with the Sdk.targets --> | |||
| <DynamicCodeSupport>false</DynamicCodeSupport> | |||
There was a problem hiding this comment.
Nice catch! These are difficult to detect when something goes wrong at runtime.
There was a problem hiding this comment.
I was under the impression we'd only do AOT on helix, not actual trimming. @steveisok how does this work?
There was a problem hiding this comment.
The new default for the property should affect many more cases than just AOT on helix so this doesn't sounds like the correct place for this fix.
There was a problem hiding this comment.
I was under the impression we'd only do AOT on helix, not actual trimming. @steveisok how does this work?
If you want trimming + AOT on helix, both have to occur in the same place. Otherwise, you have to send individual copies of the trimmed shared framework for each test from the build machine.
There was a problem hiding this comment.
That might not be as painful as it seemed initially.
There was a problem hiding this comment.
@akoeplinger Since we perform trimming on Helix, we can move this to the Directory.Build.props file. However, it will not have effect on other components.
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description
This PR re-enables the trimming of library tests on Apple mobile platforms. This change prevents the default setting of
DynamicCodeSupport=truefrom ILLink targets that are imported. The regression was introduced in #103594.With this change, the issue mentioned in #82637 has been mitigated. The tracking issue will remain open as there are separate reliability-related problems that still need to be addressed.