Skip to content
Quarkus CI

Fix native integration narayana-lra LRAParticipantTestNativeIT test #63563

Sign in to view logs

Fix native integration narayana-lra LRAParticipantTestNativeIT test

Fix native integration narayana-lra LRAParticipantTestNativeIT test #63563

Re-run triggered April 8, 2026 21:47
@quarkus-botquarkus-bot[bot]
#53510
jedla97:fix-narayana-lra-it-native
Status Success
Total duration 22m 45s
Artifacts 8

ci-actions-incremental.yml

on: pull_request
Wait for approval if Dependabot
3s
Wait for approval if Dependabot
Configure jobs
16s
Configure jobs
Attach pull request number
3s
Attach pull request number
CI Sanity Check
32s
CI Sanity Check
Initial JDK 17 Build
16m 5s
Initial JDK 17 Build
Calculate Test Jobs
12s
Calculate Test Jobs
Matrix: native-tests
Matrix: devtools-tests
Matrix: gradle-tests
Matrix: jvm-tests
Matrix: kubernetes-tests
Matrix: maven-tests
Matrix: platform-tests
Matrix: quickstarts-tests
Matrix: virtual-thread-native-tests
MicroProfile TCKs Tests
0s
MicroProfile TCKs Tests
Upload build stats to collector
0s
Upload build stats to collector
Build report
31s
Build report
Fit to window
Zoom out
Zoom in

Annotations

9 warnings and 5 notices
Initial JDK 17 Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
Initial JDK 17 Build
RUNS_ON_INSTANCE_LAUNCHED_AT environment variable not found. Cannot compute cost.
JVM Integration Tests - JDK 17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
JVM Integration Tests - JDK 17
RUNS_ON_INSTANCE_LAUNCHED_AT environment variable not found. Cannot compute cost.
JVM Integration Tests - JDK 25
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
JVM Integration Tests - JDK 25
RUNS_ON_INSTANCE_LAUNCHED_AT environment variable not found. Cannot compute cost.
JVM Integration Tests - JDK 21
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
JVM Integration Tests - JDK 25 Semeru
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
JVM Integration Tests - JDK 17 Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/develocity-actions/setup-maven@v2.1. 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/
Configure jobs
Resolved configuration:
Configure jobs
Resolving Runs-On configuration with:
Initial JDK 17 Build
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.
JVM Integration Tests - JDK 17
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.
JVM Integration Tests - JDK 25
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.

Artifacts

Produced during runtime
Name Size Digest
build-reports-2-Initial JDK 17 Build
18.9 KB
sha256:0639889eb3cfdfa29869b113805cd9e1e5160748426e4e17765d1f3d58cadac1
build-reports-2-JVM Integration Tests - JDK 17
26.5 KB
sha256:135c85b07176c7aa1d6d7a9df2c35805619f4cdc1589cff5b17285910f09a602
build-reports-2-JVM Integration Tests - JDK 17 Windows
11.5 KB
sha256:168e46f69ea7a8540a1de9b9af9e4ed4e98fc7f4e34f8b69308873d80c21f852
build-reports-2-JVM Integration Tests - JDK 21
26.8 KB
sha256:f28323c924f284f253a4420e8c0e125e825c3125ab682772781cbc03feb53906
build-reports-2-JVM Integration Tests - JDK 25
26.7 KB
sha256:03b7192121e33a3ae4e0193b52ef9bb964df109b57d47ce900b9bd2b0d680159
build-reports-2-JVM Integration Tests - JDK 25 Semeru
28.1 KB
sha256:ace7527dabc794dd3624209533069b01283db1413f5588a890de484d586e6f08
m2-content
134 MB
sha256:aa2a362fe745c7d0d029b9c5fffd32d521002dcd9180b95f8abf4662d29de007
pull-request-number-53510
159 Bytes
sha256:53c6bda5557d9aef0e42eddf145300d80525831477336203072c8a67bcb66d41