kbcli: to v0.9.1-beta.31 K3S:1.28 #113
JashBooke2e-kbcli-k3s.yml
on: workflow_dispatch
check
6s
k3s
/
...
/
test apecloud-postgresql
48m 26s
k3s
/
...
/
test camellia-redis-proxy
56m 46s
k3s
/
...
/
remove apecloud-mysql runner
4s
k3s
/
...
/
remove apecloud-postgresql runner
6s
k3s
/
...
/
remove camellia-redis-proxy runner
7s
k3s
/
...
/
enable-runner
30s
Annotations
48 errors and 2 warnings
|
k3s / test-flink / test flink
Process completed with exit code 1.
|
|
k3s / test-dmdb / test dmdb
Process completed with exit code 1.
|
|
k3s / test-asmysql / test asmysql
Process completed with exit code 1.
|
|
k3s / test-ggml / test ggml
Process completed with exit code 1.
|
|
k3s / test-mariadb / test mariadb
Process completed with exit code 1.
|
|
k3s / test-clickhouse / test clickhouse
Process completed with exit code 1.
|
|
k3s / test-etcd / test etcd
Process completed with exit code 1.
|
|
k3s / test-apecloud-postgresql / test apecloud-postgresql
Process completed with exit code 1.
|
|
k3s / test-elasticsearch / test elasticsearch
Process completed with exit code 1.
|
|
k3s / test-greptimedb / test greptimedb
Process completed with exit code 1.
|
|
k3s / test-foxlake / test foxlake
Process completed with exit code 1.
|
|
k3s / test-halo / test halo
Process completed with exit code 1.
|
|
k3s / test-camellia-redis-proxy / test camellia-redis-proxy
Process completed with exit code 1.
|
|
k3s / test-influxdb / test influxdb
Process completed with exit code 1.
|
|
k3s / test-minio / test minio
Process completed with exit code 1.
|
|
k3s / test-kafka / test kafka
Process completed with exit code 1.
|
|
k3s / test-mysqlscale / test mysqlscale
Process completed with exit code 1.
|
|
k3s / test-opengauss / test opengauss
Process completed with exit code 1.
|
|
k3s / test-official-pg / test official-pg
Process completed with exit code 1.
|
|
k3s / test-nebula / test nebula
Process completed with exit code 1.
|
|
k3s / test-openldap / test openldap
Process completed with exit code 1.
|
|
k3s / test-oracle / test oracle
Process completed with exit code 1.
|
|
k3s / test-vllm / test vllm
Process completed with exit code 1.
|
|
k3s / test-xinference / test xinference
Process completed with exit code 1.
|
|
k3s / test-opensearch / test opensearch
Process completed with exit code 1.
|
|
k3s / test-orchestrator / test orchestrator
Process completed with exit code 1.
|
|
k3s / test-mogdb / test mogdb
Process completed with exit code 1.
|
|
k3s / test-pika / test pika
Process completed with exit code 1.
|
|
k3s / test-orioledb / test orioledb
Process completed with exit code 1.
|
|
k3s / test-risingwave / test risingwave
Process completed with exit code 1.
|
|
k3s / test-polardbx / test polardbx
Process completed with exit code 1.
|
|
k3s / test-solr / test solr
Process completed with exit code 1.
|
|
k3s / test-yashandb / test yashandb
Process completed with exit code 1.
|
|
k3s / test-weaviate / test weaviate
Process completed with exit code 1.
|
|
k3s / test-tdengine / test tdengine
Process completed with exit code 1.
|
|
k3s / test-zookeeper / test zookeeper
Process completed with exit code 1.
|
|
k3s / test-tidb / test tidb
Process completed with exit code 1.
|
|
k3s / test-milvus / test milvus
Process completed with exit code 1.
|
|
k3s / test-starrocks / test starrocks
Process completed with exit code 1.
|
|
k3s / test-apecloud-mysql / test apecloud-mysql
The self-hosted runner: eks-runner-k3d-x7szc-wbx2x lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-postgresql / test postgresql
The self-hosted runner: eks-runner-k3d-x7szc-jmmd9 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-mongodb / test mongodb
The self-hosted runner: eks-runner-k3d-x7szc-sfp8l lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-qdrant / test qdrant
The self-hosted runner: eks-runner-k3d-x7szc-mfxr8 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-pulsar / test pulsar
The self-hosted runner: eks-runner-k3d-x7szc-vrzhr lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-redis / test redis
The self-hosted runner: eks-runner-k3d-x7szc-jbwxn lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-redis-cluster / test redis-cluster
The self-hosted runner: eks-runner-k3d-x7szc-lnchf lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-smartengine / test smartengine
The self-hosted runner: eks-runner-k3d-x7szc-hl9dx lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / test-starrocks-ent / test starrocks-ent
The self-hosted runner: eks-runner-k3d-x7szc-497nz lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
k3s / enable-runner / enable-runner
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/setup-kubectl@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
k3s / disable-runner / enable-runner
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/setup-kubectl@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|