[3.27] Backport detection of Junit misconfiguration #63640
Annotations
10 errors, 2 warnings, and 1 notice
|
Build
Could not initialize class org.jboss.threads.JDKSpecific$ThreadAccess
|
|
Build
--add-opens java.base/java.lang=ALL-UNNAMED
|
|
Build
Could not initialize class org.jboss.threads.JDKSpecific$ThreadAccess
|
|
Build
--add-opens java.base/java.lang=ALL-UNNAMED
|
|
Build
Could not initialize class org.jboss.threads.JDKSpecific$ThreadAccess
|
|
Build
--add-opens java.base/java.lang=ALL-UNNAMED
|
|
Build
Could not initialize class org.jboss.threads.JDKSpecific$ThreadAccess
|
|
Build
--add-opens java.base/java.lang=ALL-UNNAMED
|
|
Build
Could not initialize class org.jboss.threads.JDKSpecific$ThreadAccess
|
|
Build
--add-opens java.base/java.lang=ALL-UNNAMED
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/download-artifact@v5, actions/setup-java@v4, actions/upload-artifact@v4, gradle/develocity-actions/setup-maven@v1.4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Post Run runs-on/action@v2
RUNS_ON_INSTANCE_LAUNCHED_AT environment variable not found. Cannot compute cost.
|
|
Set up runner
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
|
Loading