Build and Test Scheduled On 3.3 #1416
build-and-test-scheduled-3.3.yml
on: schedule
build-source
15m 20s
Matrix: unit-test-prepare
integration-test-prepare
3s
samples-test-prepare
5s
license
1m 11s
error-code-inspecting
6m 5s
native-image-inspecting
6m 3s
Matrix: unit-test-fastjson2
Matrix: unit-test
Matrix: integration-test-job
Matrix: samples-test-job
Matrix: integration-test-result
Matrix: samples-test-result
Annotations
68 errors, 108 warnings, and 1 notice
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 17)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=APPLICATION_FIRST&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170212506&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 17)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=FORCE_INTERFACE&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170214348&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=APPLICATION_FIRST&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170233826&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=FORCE_INTERFACE&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170235476&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 21)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=APPLICATION_FIRST&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170229349&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 21)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=FORCE_INTERFACE&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170230805&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=APPLICATION_FIRST&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170210888&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.18.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=FORCE_INTERFACE&pid=17&protocol=dubbo®ister.ip=172.18.0.4&release=3.3.3-SNAPSHOT&side=consumer&sticky=false×tamp=1732170212579&unloadClusterRelated=false to the consumer 172.18.0.4 use dubbo version 3.3.3-SNAPSHOT
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.173:30389 -> /10.1.0.173:39028
|
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.173:32560 -> /10.1.0.173:50014
|
Unit Test On ubuntu-latest (JDK: 8, Serialization: fastjson2)
/10.1.0.152:32931 -> /10.1.0.152:35814
|
Unit Test On ubuntu-latest (JDK: 8, Serialization: fastjson2)
/10.1.0.152:32457 -> /10.1.0.152:54348
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Unit Test On ubuntu-latest (JDK: 17, Serialization: fastjson2)
/10.1.0.150:31829 -> /10.1.0.150:54438
|
Unit Test On ubuntu-latest (JDK: 17, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On ubuntu-latest (JDK: 21)
/10.1.0.70:31212 -> /10.1.0.70:57576
|
Unit Test On ubuntu-latest (JDK: 21)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On ubuntu-latest (JDK: 21, Serialization: fastjson2)
/10.1.0.62:36040 -> /10.1.0.62:55672
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Unit Test On ubuntu-latest (JDK: 17)
/10.1.0.133:33064 -> /10.1.0.133:50560
|
Unit Test On ubuntu-latest (JDK: 11)
/10.1.0.121:34307 -> /10.1.0.121:47232
|
Unit Test On ubuntu-latest (JDK: 11)
/10.1.0.121:31069 -> /10.1.0.121:60306
|
Unit Test On ubuntu-latest (JDK: 11, Serialization: fastjson2)
/10.1.0.56:30744 -> /10.1.0.56:52748
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Unit Test On windows-latest (JDK: 21, Serialization: fastjson2)
/172.20.192.1:39259 -> /172.20.192.1:58707
|
Unit Test On windows-latest (JDK: 21, Serialization: fastjson2)
/172.20.192.1:34101 -> /172.20.192.1:58714
|
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
/172.24.128.1:30205 -> /172.24.128.1:61703
|
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
/172.24.128.1:32842 -> /172.24.128.1:61803
|
Unit Test On windows-latest (JDK: 17, Serialization: fastjson2)
/172.30.176.1:31763 -> /172.30.176.1:53133
|
Unit Test On windows-latest (JDK: 17, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On windows-latest (JDK: 8, Serialization: fastjson2)
/172.30.128.1:32014 -> /172.30.128.1:65519
|
Unit Test On windows-latest (JDK: 21)
/172.29.48.1:36327 -> /172.29.48.1:51460
|
Unit Test On windows-latest (JDK: 21)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On windows-latest (JDK: 11)
/172.19.16.1:32258 -> /172.19.16.1:56724
|
Unit Test On windows-latest (JDK: 11)
/172.19.16.1:30384 -> /172.19.16.1:56819
|
Unit Test On windows-latest (JDK: 8)
/172.25.208.1:36331 -> /172.25.208.1:56717
|
Unit Test On windows-latest (JDK: 8)
/172.25.208.1:36481 -> /172.25.208.1:56810
|
Unit Test On windows-latest (JDK: 17)
/172.28.224.1:38572 -> /172.28.224.1:64577
|
Unit Test On windows-latest (JDK: 17)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 21)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 8)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 17)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Preparation for Unit Test On ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Preparation for Unit Test On windows-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
license
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
|
build-source
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 2 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 5 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On ubuntu-latest (JDK: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 8, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 17, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On ubuntu-latest (JDK: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 21, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On ubuntu-latest (JDK: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On ubuntu-latest (JDK: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On ubuntu-latest (JDK: 11, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 21, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 17, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 8, Serialization: fastjson2)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On windows-latest (JDK: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On windows-latest (JDK: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On windows-latest (JDK: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Unit Test On windows-latest (JDK: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unit Test On windows-latest (JDK: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Integration Test on ubuntu-latest (JobId: 2 JavaVer: 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
native-image-inspecting
A new GraalVM release is available! Please consider upgrading to GraalVM for JDK 17. Instructions: https://github.com/graalvm/setup-graalvm#migrating-from-graalvm-223-or-earlier-to-the-new-graalvm-for-jdk-17-and-later
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
error-inspection-result
|
602 Bytes |
|
integration-test-list
|
2.17 KB |
|
integration-test-result-11
|
445 Bytes |
|
integration-test-result-17
|
444 Bytes |
|
integration-test-result-21
|
449 Bytes |
|
integration-test-result-8
|
441 Bytes |
|
samples-test-list
|
3.13 KB |
|
samples-test-result-11
|
633 Bytes |
|
samples-test-result-17
|
626 Bytes |
|
samples-test-result-21
|
627 Bytes |
|
samples-test-result-8
|
630 Bytes |
|