Skip to content

Commit 10ef40d

Browse files
[tests] enable .NET 7 LLVM tests without Profiled AOT
Context: dotnet/runtime#68914 We found that the issue with LLVM only occurs when using Profiled AOT. This is enabled by default for `Release` builds in .NET 6+, so let's try using `-p:AndroidEnableProfiledAot=false`. This at least gets some of our LLVM test coverage running again.
1 parent a7217cb commit 10ef40d

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

build-tools/automation/azure-pipelines.yaml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -697,13 +697,11 @@ stages:
697697

698698
- template: yaml-templates/apk-instrumentation.yaml
699699
parameters:
700-
# TODO: disable LLVM test, see: https://github.com/dotnet/runtime/issues/68914
701-
condition: false
702700
configuration: $(XA.Build.Configuration)
703701
testName: Mono.Android.NET_Tests-AotLlvm
704702
project: tests/Mono.Android-Tests/Runtime-Microsoft.Android.Sdk/Mono.Android.NET-Tests.csproj
705703
testResultsFiles: TestResult-Mono.Android.NET_Tests-$(XA.Build.Configuration)AotLlvm.xml
706-
extraBuildArgs: -p:TestsFlavor=AotLlvm -p:EnableLlvm=true
704+
extraBuildArgs: -p:TestsFlavor=AotLlvm -p:EnableLlvm=true -p:AndroidEnableProfiledAot=false
707705
artifactSource: bin/Test$(XA.Build.Configuration)/$(DotNetTargetFramework)-android/Mono.Android.NET_Tests-Signed.aab
708706
artifactFolder: $(DotNetTargetFramework)-AotLlvm
709707
useDotNet: true

0 commit comments

Comments
 (0)