Repository navigation
gax-grpc: Surefire <test> pattern restricts the unit test run to a single test #14572
Description
In sdk-platform-java/gax-java/gax-grpc/pom.xml, the Surefire configuration is:
<test>!InstantiatingGrpcChannelProviderTest#testLogDirectPathMisconfig_AttemptDirectPathNotSetAndAttemptDirectPathXdsSetViaEnv_warns,!InstantiatingGrpcChannelProviderTest#canUseDirectPath_directPathEnvVarNotSet_attemptDirectPathIsTrue,InstantiatingGrpcChannelProviderTest#testLogDirectPathMisconfigWrongCredential</test>The last entry has no leading !. Surefire therefore treats it as an inclusion pattern: only InstantiatingGrpcChannelProviderTest#testLogDirectPathMisconfigWrongCredential runs, and the rest of the gax-grpc unit tests are skipped. This includes ChannelPoolTest, GrpcCallContextTest, GrpcClientCallsTest, and all other InstantiatingGrpcChannelProviderTest cases.
This seems to have been introduced when sdk-platform-java was migrated into the monorepo ("chore(sdk-platform-java): apply manual changes"). Before that, the line contained only the first exclusion.
Evidence: in the sdk-platform-java units job, gax-grpc reports Tests run: 1. The only test class run is InstantiatingGrpcChannelProviderTest. An example is a recent run on main's release-please branch (job 110584625307). On a branch with the stray inclusion removed, the same job runs the full gax-grpc suite.
Expected: keep the two exclusions (tests that depend on environment variables), and run the rest of the gax-grpc unit suite.
Activity
jinseopkim0 commentedon Oct 2, 2026
Thanks for opening this issue. If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response. We try to review GitHub issues on a regular basis, however we cannot guarantee an SLO.
test(gax-grpc): run the full unit test suite in CI (#14573)