Pipe: Fixed the bug that different types in schema snapshot transfer may cause transfer failure #11123
Triggered via pull request
September 26, 2024 02:26
Caideyipi
Status
Success
Total duration
1h 45m 48s
Artifacts
–
pipe-it-2cluster.yml
on: pull_request
Matrix: auto-create-schema
Matrix: manual-create-schema
Matrix: subscription-arch-verification
Matrix: subscription-regression-consumer
Matrix: subscription-regression-misc
Annotations
3 errors
|
auto-create-schema (17, LightWeightStandaloneMode, ubuntu-latest)
[127.0.0.1:11617, 127.0.0.1:13201, 127.0.0.1:14521, 127.0.0.1:20890] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
auto-create-schema (17, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:19240, 127.0.0.1:21121, 127.0.0.1:11947, 127.0.0.1:12585] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
auto-create-schema (17, HighPerformanceMode, ubuntu-latest)
[127.0.0.1:19383, 127.0.0.1:21297, 127.0.0.1:16743, 127.0.0.1:17634] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|