Production #7606
Dousir9production.yml
on: merge_group
changes
19s
Matrix: linux / build
Matrix: linux / build_udf
Matrix: linux / sqllogic / cluster
Matrix: linux / sqllogic / ee
Matrix: linux / sqllogic / stage
Matrix: linux / sqllogic / standalone
Matrix: linux / sqllogic / standalone_minio
Matrix: linux / sqllogic / standalone_no_table_meta_cache
linux
/
test_metactl
50s
linux
/
test_compat_meta_query
1m 22s
linux
/
test_compat_fuse
3m 49s
linux
/
test_compat_meta_meta
37s
linux
/
test_logs
24s
linux
/
test_meta_cluster
26s
linux
/
test_stateless_standalone
3m 25s
linux
/
test_stateless_cluster
4m 40s
linux
/
test_stateful_standalone
14m 51s
linux
/
test_stateful_cluster
3m 49s
linux
/
test_stateful_large_data
0s
linux
/
test_stateful_iceberg_rest
37s
linux
/
test_ee_standalone
1m 5s
linux
/
test_ee_standalone_background
40s
linux
/
test_ee_management_mode
19s
linux
/
...
/
management_mode
20s
linux
/
...
/
standalone_udf_server
52s
linux
/
...
/
standalone_cloud
28s
ready
8s
Annotations
19 errors
|
linux / sqllogic / standalone_minio (query, http, parquet)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone_minio (query, http, parquet)
The self-hosted runner: databend-4c8g-x64-9wrkd-h2774 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.
|
|
linux / sqllogic / standalone_minio (query, http, native)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone_minio (query, http, native)
The self-hosted runner: databend-4c8g-x64-9wrkd-cfllp 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.
|
|
linux / sqllogic / standalone (ydb, http)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (ydb, http)
The self-hosted runner: databend-4c8g-x64-9wrkd-6gss7 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.
|
|
linux / test_stateful_standalone
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / test_stateful_standalone
The self-hosted runner: databend-4c8g-x64-9wrkd-77jnp 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.
|
|
linux / sqllogic / standalone (base, http)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (base, http)
The self-hosted runner: databend-4c8g-x64-9wrkd-b2rxt 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.
|
|
linux / sqllogic / standalone (duckdb, http)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (duckdb, http)
The self-hosted runner: databend-4c8g-x64-9wrkd-c98b7 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.
|
|
linux / sqllogic / standalone (tpch, http)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (tpch, mysql)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (tpch, http)
The self-hosted runner: databend-4c8g-x64-9wrkd-rc9k7 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.
|
|
linux / sqllogic / standalone (tpch, mysql)
The self-hosted runner: databend-4c8g-x64-9wrkd-sdzhz 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.
|
|
linux / sqllogic / standalone (duckdb, mysql)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
linux / sqllogic / standalone (duckdb, mysql)
The self-hosted runner: databend-4c8g-x64-9wrkd-gp2xm 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.
|
|
ready
Build failed, not ready to merge
|