-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Disable Android tests in default CI set for now #115956
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
Conversation
Workaround for dotnet#115955
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.
Pull Request Overview
This PR provides a workaround for issue #115955 by disabling Android tests in the default CI set.
- Updates the build arguments in the runtime.yml pipeline configuration.
- Disables test assemblies by changing the parameter from "/p:RunSmokeTestsOnly=true" to "/p:TestAssemblies=false".
@@ -956,7 +956,7 @@ extends: | |||
jobParameters: | |||
testGroup: innerloop | |||
nameSuffix: AllSubsets_CoreCLR | |||
buildArgs: -s clr.runtime+clr.alljits+clr.corelib+clr.nativecorelib+clr.tools+clr.packages+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:RunSmokeTestsOnly=true | |||
buildArgs: -s clr.runtime+clr.alljits+clr.corelib+clr.nativecorelib+clr.tools+clr.packages+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:TestAssemblies=false |
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.
Consider adding an inline comment explaining the rationale for disabling test assemblies in the CI pipeline to support future maintainers in understanding this workaround.
Copilot uses AI. Check for mistakes.
Tagging subscribers to this area: @hoyosjs |
@@ -956,7 +956,7 @@ extends: | |||
jobParameters: | |||
testGroup: innerloop | |||
nameSuffix: AllSubsets_CoreCLR | |||
buildArgs: -s clr.runtime+clr.alljits+clr.corelib+clr.nativecorelib+clr.tools+clr.packages+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:RunSmokeTestsOnly=true | |||
buildArgs: -s clr.runtime+clr.alljits+clr.corelib+clr.nativecorelib+clr.tools+clr.packages+libs+libs.tests+host+packs -c $(_BuildConfig) /p:ArchiveTests=true /p:TestAssemblies=false |
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.
So disable the project reference to library tests? if this correctly passes Helix in the next step- no issue. Just unclear what we are sending at that point?
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.
This is revert of this line https://github.com/dotnet/runtime/pull/114148/files#diff-e2e027b9777fc35f4a8243db97ce50f7dac99b3cee9465c5325d283c34d2d872R959 from the PR that enabled Android tests a few days ago. I believe that this is only going to validate the build now.
Couple things ran - it's quick as far as I can tell though. |
/ba-g infrastructure failure with no log |
Workaround for #115955