Build and Test Scheduled On 3.1 #3062
build-and-test-scheduled-3.1.yml
on: schedule
build-source
10m 26s
Matrix: unit-test-prepare
integration-test-prepare
4s
samples-test-prepare
6s
license
1m 3s
error-code-inspecting
5m 28s
native-image-inspecting
9m 5s
Matrix: unit-test-fastjson2
Matrix: unit-test
Matrix: integration-test-job
Matrix: samples-test-job
Matrix: integration-test-result
Matrix: samples-test-result
Annotations
75 errors, 68 warnings, and 1 notice
native-image-inspecting
Process completed with exit code 127.
|
Unit Test On ubuntu-latest (JDK: 21)
Process completed with exit code 1.
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 11)
Process completed with exit code 1.
|
Samples Test on ubuntu-latest (JobId: 1 JavaVer: 8)
Process completed with exit code 1.
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Process completed with exit code 1.
|
Samples 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
|
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: 2 JavaVer: 8)
Process completed with exit code 1.
|
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: 2 JavaVer: 11)
Process completed with exit code 1.
|
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: 5 JavaVer: 8)
Process completed with exit code 1.
|
Samples Test on ubuntu-latest (JobId: 3 JavaVer: 8)
Process completed with exit code 1.
|
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: 3 JavaVer: 11)
Process completed with exit code 1.
|
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: 11)
Process completed with exit code 1.
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 8)
Process completed with exit code 1.
|
Integration Test on ubuntu-latest (JobId: 5 JavaVer: 11)
Process completed with exit code 1.
|
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: 11)
Process completed with exit code 1.
|
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: 8)
Process completed with exit code 1.
|
Unit Test On windows-latest (JDK: 21)
Process completed with exit code 1.
|
Integration Test on ubuntu-latest (JobId: 1 JavaVer: 8)
Process completed with exit code 1.
|
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: 11)
Process completed with exit code 1.
|
Unit Test On windows-latest (JDK: 17, Serialization: fastjson2)
Process completed with exit code 1.
|
Samples Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Process completed with exit code 1.
|
Samples 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
|
samples-test-result (8)
Process completed with exit code 1.
|
samples-test-result (11)
Process completed with exit code 1.
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 8)
Process completed with exit code 1.
|
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: 3 JavaVer: 11)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 11)
Process completed with exit code 1.
|
Integration 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
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
|
Integration Test on ubuntu-latest (JobId: 4 JavaVer: 11)
Process completed with exit code 1.
|
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
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 8)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
|
Integration Test on ubuntu-latest (JobId: 3 JavaVer: 8)
Process completed with exit code 1.
|
Integration 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
|
integration-test-result (11)
Process completed with exit code 1.
|
integration-test-result (8)
The job was canceled because "_11" failed.
|
integration-test-result (8)
Process completed with exit code 1.
|
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.88:31895 -> /10.1.0.88:51186
|
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.88:33026 -> /10.1.0.88:45666
|
Unit Test On ubuntu-latest (JDK: 17)
/10.1.0.226:34508 -> /10.1.0.226:55800
|
Unit Test On ubuntu-latest (JDK: 17)
/10.1.0.226:33605 -> /10.1.0.226:39756
|
Unit Test On ubuntu-latest (JDK: 17)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On ubuntu-latest (JDK: 17)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On windows-latest (JDK: 8)
/172.23.48.1:34578 -> /172.23.48.1:50170
|
Unit Test On windows-latest (JDK: 8)
/172.23.48.1:31539 -> /172.23.48.1:50265
|
Unit Test On windows-latest (JDK: 11)
/172.19.112.1:39284 -> /172.19.112.1:60801
|
Unit Test On windows-latest (JDK: 11)
/172.19.112.1:38936 -> /172.19.112.1:60900
|
Unit Test On windows-latest (JDK: 17)
/172.20.128.1:32147 -> /172.20.128.1:64816
|
Unit Test On windows-latest (JDK: 17)
/172.20.128.1:34262 -> /172.20.128.1:64823
|
Unit Test On windows-latest (JDK: 17)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On windows-latest (JDK: 17)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
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, Serialization: fastjson2)
/10.1.0.130:39595 -> /10.1.0.130:44944
|
Unit Test On ubuntu-latest (JDK: 21, Serialization: fastjson2)
/10.1.0.130:32753 -> /10.1.0.130:34076
|
Unit Test On ubuntu-latest (JDK: 21, 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, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
|
Unit Test On ubuntu-latest (JDK: 11, Serialization: fastjson2)
/10.1.0.24:32757 -> /10.1.0.24:43040
|
Unit Test On ubuntu-latest (JDK: 11, Serialization: fastjson2)
/10.1.0.24:31332 -> /10.1.0.24:53020
|
Unit Test On windows-latest (JDK: 21, Serialization: fastjson2)
/172.30.0.1:33509 -> /172.30.0.1:58470
|
Unit Test On windows-latest (JDK: 21, Serialization: fastjson2)
/172.30.0.1:38365 -> /172.30.0.1:58477
|
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
/172.22.240.1:39941 -> /172.22.240.1:59337
|
Unit Test On windows-latest (JDK: 8, Serialization: fastjson2)
/172.26.240.1:39609 -> /172.26.240.1:65104
|
Unit Test On windows-latest (JDK: 8, Serialization: fastjson2)
/172.26.240.1:34567 -> /172.26.240.1:65203
|
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/
|
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/
|
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: 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: 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/
|
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: 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: 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: 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: 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/
|
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: 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: 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: 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/
|
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/
|
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/
|
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/
|
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/
|
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: 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: 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/
|
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/
|
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: 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 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: 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: 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/
|
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, 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: 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 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/
|
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: 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/
|
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
|
624 Bytes |
|
integration-test-list
|
2.17 KB |
|
integration-test-result-11
|
597 Bytes |
|
integration-test-result-8
|
594 Bytes |
|
samples-test-list
|
3.13 KB |
|
samples-test-result-11
|
838 Bytes |
|
samples-test-result-8
|
833 Bytes |
|