Skip to content

Build and Test Scheduled On 3.1 #1723

Build and Test Scheduled On 3.1

Build and Test Scheduled On 3.1 #1723

Triggered via schedule December 13, 2023 12:02
Status Failure
Total duration 37m 45s
Artifacts 4
Matrix: unit-test-prepare
integration-test-prepare
4s
integration-test-prepare
license
1m 8s
license
error-code-inspecting
5m 2s
error-code-inspecting
native-image-inspecting
9m 4s
native-image-inspecting
Matrix: unit-test-fastjson2
Matrix: unit-test
Matrix: integration-test-job
Matrix: integration-test-result
Fit to window
Zoom out
Zoom in

Annotations

55 errors, 28 warnings, and 1 notice
Integration Test on ubuntu-latest (JobId: 4)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 4)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 1)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 1)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 5)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 5)
Process completed with exit code 1.
Integration Test on ubuntu-latest (JobId: 3)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
Integration Test on ubuntu-latest (JobId: 3)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
Integration Test on ubuntu-latest (JobId: 3)
Process completed with exit code 1.
Unit Test On ubuntu-latest (JDK: 19)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On ubuntu-latest (JDK: 19)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.136:39887 -> /10.1.0.136:40618
Unit Test On ubuntu-latest (JDK: 8)
/10.1.0.136:35230 -> /10.1.0.136:45602
Integration Test on ubuntu-latest (JobId: 3)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
Integration Test on ubuntu-latest (JobId: 3)
Attribute 'qos-port' is not allowed to appear in element 'dubbo:application'.
Integration Test on ubuntu-latest (JobId: 3)
Process completed with exit code 1.
Unit Test On ubuntu-latest (JDK: 8, Serialization: fastjson2)
/10.1.0.178:33641 -> /10.1.0.178:39334
Unit Test On ubuntu-latest (JDK: 8, Serialization: fastjson2)
/10.1.0.178:35615 -> /10.1.0.178:48882
Unit Test On ubuntu-latest (JDK: 19, Serialization: fastjson2)
/10.1.0.189:36225 -> /10.1.0.189:37752
Unit Test On ubuntu-latest (JDK: 19, Serialization: fastjson2)
/10.1.0.189:38833 -> /10.1.0.189:49602
Unit Test On ubuntu-latest (JDK: 19, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On ubuntu-latest (JDK: 19, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
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: 17, Serialization: fastjson2)
/10.1.0.103:33309 -> /10.1.0.103:35776
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: 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: 19, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On windows-latest (JDK: 19, Serialization: fastjson2)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On windows-latest (JDK: 19, Serialization: fastjson2)
Process completed with exit code 1.
Unit Test On ubuntu-latest (JDK: 17)
/10.1.0.244:36942 -> /10.1.0.244:51722
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 ubuntu-latest (JDK: 11)
/10.1.0.121:38145 -> /10.1.0.121:34240
Unit Test On ubuntu-latest (JDK: 11, Serialization: fastjson2)
/10.1.0.102:39687 -> /10.1.0.102:49356
Unit Test On windows-latest (JDK: 19)
/172.18.128.1:32329 -> /172.18.128.1:50503
Unit Test On windows-latest (JDK: 19)
/172.18.128.1:39686 -> /172.18.128.1:50510
Unit Test On windows-latest (JDK: 19)
Cannot invoke "org.apache.dubbo.metadata.report.support.AbstractMetadataReport$MetadataReportRetry.startRetryTask()" because "this.metadataReportRetry" is null
Unit Test On windows-latest (JDK: 19)
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.29.176.1:34134 -> /172.29.176.1:50156
Unit Test On windows-latest (JDK: 8, Serialization: fastjson2)
/172.29.176.1:38197 -> /172.29.176.1:50251
Unit Test On windows-latest (JDK: 17)
/172.24.160.1:34594 -> /172.24.160.1:56838
Unit Test On windows-latest (JDK: 17)
/172.24.160.1:36594 -> /172.24.160.1:56845
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 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: 8)
/172.20.208.1:36511 -> /172.20.208.1:64733
Unit Test On windows-latest (JDK: 8)
/172.20.208.1:31456 -> /172.20.208.1:64827
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: 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: 11)
/172.26.224.1:38238 -> /172.26.224.1:55326
Unit Test On windows-latest (JDK: 11)
/172.26.224.1:36284 -> /172.26.224.1:55420
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
/172.27.128.1:33637 -> /172.27.128.1:55259
Unit Test On windows-latest (JDK: 11, Serialization: fastjson2)
/172.27.128.1:37280 -> /172.27.128.1:55353
license
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
error-code-inspecting
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)
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)
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)
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)
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)
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)
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)
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)
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)
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: 19)
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 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)
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, Serialization: fastjson2)
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: 19, Serialization: fastjson2)
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, Serialization: fastjson2)
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: 19, Serialization: fastjson2)
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 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 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, Serialization: fastjson2)
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: 19)
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, Serialization: fastjson2)
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 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 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, Serialization: fastjson2)
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 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, Serialization: fastjson2)
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/
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 Expired
1.08 KB
test-list Expired
26.5 KB
test-result-11 Expired
14.8 KB
test-result-8 Expired
14.8 KB