Pipe: Fixed the bug that disruptor queue close may block forever by not waiting real-time tsFile close #2329
Caideyipipipe-it.yml
on: pull_request
Matrix: dual-table-manual-basic
Matrix: dual-table-manual-enhanced
Matrix: dual-tree-auto-basic
Matrix: dual-tree-auto-enhanced
Matrix: dual-tree-manual
Matrix: single
Matrix: subscription-arch-verification
Matrix: subscription-regression-consumer
Matrix: subscription-regression-misc
Annotations
11 errors and 1 warning
|
dual-tree-auto-enhanced (17, ScalableSingleNodeMode, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:14829, 127.0.0.1:13762, 127.0.0.1:20296, 127.0.0.1:17755] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-tree-auto-enhanced (17, LightWeightStandaloneMode, HighPerformanceMode, ubuntu-latest)
[127.0.0.1:14191, 127.0.0.1:16677, 127.0.0.1:20956, 127.0.0.1:18085] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:17711, 127.0.0.1:19768, 127.0.0.1:14477, 127.0.0.1:11276] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-tree-auto-enhanced (17, HighPerformanceMode, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:14356, 127.0.0.1:17370, 127.0.0.1:14620, 127.0.0.1:13223] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-tree-auto-enhanced (17, PipeConsensusBatchMode, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:14532, 127.0.0.1:18085, 127.0.0.1:15357, 127.0.0.1:11749] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-tree-auto-enhanced (17, PipeConsensusStreamMode, ScalableSingleNodeMode, ubuntu-latest)
[127.0.0.1:16963, 127.0.0.1:16369, 127.0.0.1:16523, 127.0.0.1:19328] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, LightWeightStandaloneMode, ubuntu-latest)
[127.0.0.1:12882, 127.0.0.1:12365, 127.0.0.1:16721, 127.0.0.1:13311] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, PipeConsensusBatchMode, ubuntu-latest)
[127.0.0.1:14246, 127.0.0.1:12970, 127.0.0.1:17524, 127.0.0.1:16490] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, PipeConsensusStreamMode, ubuntu-latest)
[127.0.0.1:17370, 127.0.0.1:14191, 127.0.0.1:14807, 127.0.0.1:11419] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, HighPerformanceMode, ubuntu-latest)
The hosted runner: GitHub Actions 625 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
dual-table-manual-enhanced (17, HighPerformanceMode, ubuntu-latest)
[127.0.0.1:16732, 127.0.0.1:16688, 127.0.0.1:15335, 127.0.0.1:17491] with data [null, null, null, Connection Error, please check whether the network is available or the server has started.]
|
|
dual-table-manual-enhanced (17, HighPerformanceMode, ubuntu-latest)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 0 MB
|