Skip to content

Some tests are failing on Bazel CI because of JDK21 #21593

@coeuvre

Description

@coeuvre

Description of the bug:

  • //src/test/shell/bazel/android:android_local_test_integration_test
  • //src/test/shell/bazel/android:android_local_test_integration_test_with_head_android_tools
  • //src/java_tools/junitrunner/javatests/com/google/testing/junit/runner:AllTests
  • //src/java_tools/junitrunner/javatests/com/google/testing/junit/runner:antxmlresultwriter_integration_test
  • //src/java_tools/junitrunner/javatests/com/google/testing/junit/runner:junit4_testbridge_integration_test
  • //src/java_tools/junitrunner/javatests/com/google/testing/junit/runner:utf8_test_log_test

are failing with following error on Bazel CI because we recently upgrade the host JDK to JDK21:

java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release
	at java.base/java.lang.System.setSecurityManager(System.java:429)
	at com.google.testing.junit.runner.junit4.JUnit4Runner.installSecurityManager(JUnit4Runner.java:256)
	at com.google.testing.junit.runner.junit4.JUnit4Runner.run(JUnit4Runner.java:113)
	at com.google.testing.junit.runner.BazelTestRunner.runTestsInSuite(BazelTestRunner.java:145)
	at com.google.testing.junit.runner.BazelTestRunner.main(BazelTestRunner.java:76)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at com.google.testing.coverage.JacocoCoverageRunner.main(JacocoCoverageRunner.java:592)

https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/20432#018e13ed-069f-43fd-b7fb-b0bbbff0ef0a

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

No response

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    team-OSSIssues for the Bazel OSS team: installation, release processBazel packaging, websiteteam-Rules-JavaIssues for Java rulestype: buguntriaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions