Test

Public

Run fast unit and integration tests

wip: remove all the things

#102190
/
teskje:cluster-transport-protocol/5acdef69beb7(#32171)
Failed in 1h 7m
:pipeline:
mkpipeline
:rust: Cargo test
Restart test
Yugabyte CDC tests
Short Zippy
Feature benchmark (Kafka only)
Persistence tests
Cluster isolation test
chbench smoke test
Metabase smoke test
dbt-materialize tests
Storage Usage Table Test
Tracing Fast Path
mz-debug tool
Jan Teske
Jan Teske
Created
Triggered from Webhook

:rust: Cargo test failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

        FAIL [  60.739s] mz-environmentd::auth test_refresh_dropped_session

     TIMEOUT [ 190.066s] mz-balancerd::server test_balancer

        FAIL [  69.353s] mz-environmentd::auth test_refresh_dropped_session_lru

        FAIL [ 133.392s] mz-environmentd::pgwire test_pgtest

        FAIL [ 154.318s] mz-environmentd::pgwire test_pgtest_mz

     TIMEOUT [ 240.079s] mz-environmentd::bootstrap_builtin_clusters test_zero_replication_factor_no_replicas

     TIMEOUT [ 240.077s] mz-environmentd::pgwire test_bind_params

     TIMEOUT [ 240.054s] mz-environmentd::pgwire test_conn_startup

        FAIL [  11.192s] mz-environmentd::server test_cancel_dataflow_removal

        FAIL [  11.978s] mz-environmentd::server test_cancel_insert_select

     TIMEOUT [ 240.076s] mz-environmentd::pgwire test_record_types

        FAIL [  11.937s] mz-environmentd::server test_cancel_long_select

        FAIL [  70.896s] mz-environmentd::server test_cancel_read_then_write

     TIMEOUT [ 240.075s] mz-environmentd::server concurrent_cluster_drop

        FAIL [  11.069s] mz-environmentd::server test_closing_connection_for_long_select

     TIMEOUT [ 240.084s] mz-environmentd::server copy_from

     TIMEOUT [ 240.059s] mz-environmentd::server smoketest_webhook_source

     TIMEOUT [ 240.064s] mz-environmentd::server test_builtin_connection_alterations_are_preserved_across_restarts

     TIMEOUT [ 240.077s] mz-environmentd::server test_cancel_ws

     TIMEOUT [ 240.060s] mz-environmentd::server test_concurrent_id_reuse

     TIMEOUT [ 240.062s] mz-environmentd::server test_default_cluster_sizes

     TIMEOUT [ 240.067s] mz-environmentd::server test_double_encoded_json

     TIMEOUT [ 240.066s] mz-environmentd::server test_durable_oids

     TIMEOUT [ 240.070s] mz-environmentd::server test_enable_internal_statement_logging

        FAIL [  41.694s] mz-environmentd::server test_http_sql

     TIMEOUT [ 240.081s] mz-environmentd::server test_github_20262

     TIMEOUT [ 240.040s] mz-environmentd::server test_github_25388

        FAIL [  71.365s] mz-environmentd::server test_statement_logging_immediate

     TIMEOUT [ 240.099s] mz-environmentd::server test_leader_promotion_mixed_code_version

     TIMEOUT [ 240.088s] mz-environmentd::server test_old_storage_usage_records_are_reaped_on_restart

     TIMEOUT [ 240.068s] mz-environmentd::server test_persistence

     TIMEOUT [ 240.079s] mz-environmentd::server test_statement_logging_basic

     TIMEOUT [ 240.076s] mz-environmentd::server test_statement_logging_subscribes

     TIMEOUT [ 240.069s] mz-environmentd::server test_statement_logging_throttling

     TIMEOUT [ 240.080s] mz-environmentd::server test_storage_usage_doesnt_update_between_restarts

     TIMEOUT [ 240.058s] mz-environmentd::server test_storage_usage_records_are_not_cleared_on_restart

     TIMEOUT [ 240.065s] mz-environmentd::server test_storage_usage_updates_between_restarts

     TIMEOUT [ 240.071s] mz-environmentd::server test_webhook_url_notice

     TIMEOUT [ 240.069s] mz-environmentd::server webhook_concurrent_actions

     TIMEOUT [ 240.061s] mz-environmentd::server webhook_concurrent_swap

     TIMEOUT [ 600.083s] mz-environmentd::server test_storage_usage_collection_interval

     TIMEOUT [ 600.091s] mz-environmentd::server test_storage_usage_collection_interval_timestamps

     TIMEOUT [ 240.077s] mz-environmentd::sql test_auto_run_on_introspection_feature_disabled

     TIMEOUT [ 240.074s] mz-environmentd::sql test_auto_run_on_introspection_feature_enabled

     TIMEOUT [ 240.090s] mz-environmentd::sql test_auto_run_on_introspection_per_replica_relations

     TIMEOUT [ 240.053s] mz-environmentd::sql test_builtin_schemas

     TIMEOUT [ 240.072s] mz-environmentd::sql test_concurrent_writes

     TIMEOUT [ 240.086s] mz-environmentd::sql test_dont_drop_sinks_twice

     TIMEOUT [ 240.085s] mz-environmentd::sql test_emit_timestamp_notice

     TIMEOUT [ 240.042s] mz-environmentd::sql test_empty_subscribe_notice

     TIMEOUT [ 240.046s] mz-environmentd::sql test_explain_as_of

     TIMEOUT [ 240.045s] mz-environmentd::sql test_explain_timestamp_blocking

        FAIL [  10.975s] mz-environmentd::sql test_peek_on_dropped_cluster

     TIMEOUT [ 240.084s] mz-environmentd::sql test_github_12951

     TIMEOUT [ 240.058s] mz-environmentd::sql test_linearizability

     TIMEOUT [ 240.069s] mz-environmentd::sql test_load_generator

     TIMEOUT [ 240.072s] mz-environmentd::sql test_mz_sessions

        FAIL [  43.595s] mz-environmentd::sql test_serialized_ddl_cancel

     TIMEOUT [ 240.083s] mz-environmentd::sql test_params

     TIMEOUT [ 240.059s] mz-environmentd::sql test_peek_on_dropped_indexed_view

     TIMEOUT [ 240.074s] mz-environmentd::sql test_pg_cancel_backend

     TIMEOUT [ 240.063s] mz-environmentd::sql test_pg_cancel_dropped_role

     TIMEOUT [ 240.041s] mz-environmentd::sql test_strong_session_serializability

     TIMEOUT [ 240.071s] mz-environmentd::sql test_subcribe_continuous_progress

     TIMEOUT [ 240.058s] mz-environmentd::sql test_subscribe_basic

     TIMEOUT [ 240.072s] mz-environmentd::sql test_subscribe_consolidation

     TIMEOUT [ 240.077s] mz-environmentd::sql test_subscribe_empty_upper_frontier

     TIMEOUT [ 240.080s] mz-environmentd::sql test_subscribe_fetch_timeout
Test details & reproducer Runs the Rust-based unit tests in Debug mode. 
bin/mzcompose --find cargo-test run default

Testdrive 4 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1     | 2025-04-14T08:30:56.376062Z  thread 'tokio:work-6' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

resetting materialize state: SHOW DATABASES: connection closed

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=3 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Testdrive 7 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1     | 2025-04-14T08:29:59.341223Z  thread 'tokio:work-12' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

resetting materialize state: SHOW DATABASES: connection closed

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=6 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Testdrive 8 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1     | 2025-04-14T08:29:50.913163Z  thread 'tokio:work-15' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=7 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Testdrive 3 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1          | 2025-04-14T08:29:19.757265Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

testdrive-materialized-1     | 2025-04-14T08:30:02.154765Z  thread 'tokio:work-7' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

resetting materialize state: SHOW DATABASES: connection closed

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=2 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Testdrive 1 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1     | 2025-04-14T08:27:54.199879Z  thread 'tokio:work-8' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

resetting materialize state: SHOW DATABASES: connection closed
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=0 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Testdrive 2 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

testdrive-materialized-1          | 2025-04-14T08:26:50.235806Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

testdrive-materialized-1     | 2025-04-14T08:28:30.413860Z  thread 'tokio:work-16' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known

resetting materialize state: SHOW DATABASES: connection closed

error connecting to server: failed to lookup address information: Name or service not known: failed to lookup address information: Name or service not known
Test details & reproducer Testdrive is the basic framework and language for defining product tests under the expected-result/actual-result (aka golden testing) paradigm. A query is retried until it produces the desired result. 
BUILDKITE_PARALLEL_JOB=1 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find testdrive run default

Legacy upgrade tests (last version from docs, ignore missing) 2 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

legacy-upgrade-materialized-1     | 2025-04-14T08:31:11.494273Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:32:22.627262Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:33:57.584434Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:34:08.234704Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:35:51.909384Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:36:53.421785Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:39:35.046638Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:40:24.388684Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:41:11.885918Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:41:55.543795Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:43:10.046734Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:43:19.711383Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:44:14.351890Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:44:36.018365Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:45:39.542758Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:46:19.108742Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:46:53.823571Z  thread 'tokio:work-4' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:47:10.620014Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:48:20.323927Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:48:56.980997Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:49:14.692914Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:49:30.334372Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:50:04.018504Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:50:45.632362Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:53:01.256849Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:53:34.627155Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:54:34.289925Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:54:56.876437Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

legacy-upgrade-materialized-1     | 2025-04-14T08:56:28.553689Z  thread 'tokio:work-3' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

Docker compose failed: docker compose -f/dev/fd/4 --project-directory /var/lib/buildkite-agent/builds/hetzner-aarch64-4cpu-8gb-e144508c/materialize/test/test/legacy-upgrade run -eCLUSTER_REPLICA_SIZES testdrive --no-reset --var=upgrade-from-version=current_source --var=created-cluster=quickstart --var=mysql-root-password=p@ssw0rd --var=mysql-user-password=us3rp4ssw0rd --temp-dir=/share/tmp/upgrade-from-current_source --seed=3563203718 create-in-{any_version,*,current_source}-*.td --materialize-url=postgres://materialize@materialized:6875 --materialize-internal-url=postgres://mz_system@materialized:6877

Container legacy-upgrade-cockroach-1  Running
^^^ +++
^^^ +++
^^^ +++
^^^ +++
+++ !!! Error Report
4 errors were encountered during execution
files involved: create-in-v0.27.0-kafka-source.td create-in-v0.27.0-pg-cdc.td create-in-v0.27.0-schema-registry.td create-in-v0.38.0-range.td
Test details & reproducer Verifies that objects created in previous versions of Materialize are still operational after an upgrade. See also the newer platform-checks' upgrade scenarios. 
BUILDKITE_PARALLEL_JOB=1 BUILDKITE_PARALLEL_JOB_COUNT=2 bin/mzcompose --find legacy-upgrade run default --versions-source=docs --ignore-missing-version

Persistence tests failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

persistence-materialized-1  | 2025-04-14T08:34:34.228803Z  thread 'tokio:work-2' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty

persistence-materialized-1     | 2025-04-14T08:35:56.771998Z  thread 'tokio:work-0' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty
Test details & reproducer Basic tests for Persistence layer. 
bin/mzcompose --find persistence run default

MySQL CDC tests 2 failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

mysql-cdc-materialized-1  | 2025-04-14T08:30:27.133841Z  thread 'tokio:work-1' panicked at src/service/src/transport.rs:73:27: expected connection error: Empty
Test details & reproducer Functional test for the native (non-Debezium) MySQL sources. 
BUILDKITE_PARALLEL_JOB=1 BUILDKITE_PARALLEL_JOB_COUNT=2 bin/mzcompose --find mysql-cdc run default
Merge skew cargo checkci/test/check-merge-with-target.sh
Waited 14s
·
Ran in 9s
Agent
Lint and rustfmtbin/ci-builder run stable ci/test/lint-fast.sh
Waited 5s
·
Ran in 3m 37s
Agent
Clippy and doctestsbin/ci-builder run stable ci/test/lint-slow.sh
Waited 53s
·
Ran in 6m 55s
Agent
:rust: Cargo test
Timed Out
Waited 1m 14s
·
Ran in 1h 2m
Agent
1/8
Testdrive 1
Timed Out
Waited 12s
·
Ran in 42m 31s
Agent
2/8
Testdrive 2
Timed Out
Waited 3s
·
Ran in 42m 32s
Agent
3/8
Testdrive 3
Timed Out
Waited 1m 53s
·
Ran in 42m 43s
Agent
4/8
Testdrive 4
Timed Out
Waited 2m 1s
·
Ran in 42m 43s
Agent
5/8
Testdrive 5
Waited 2m 2s
·
Ran in 10m 14s
Agent
6/8
Testdrive 6
Waited 1m 57s
·
Ran in 9m 25s
Agent
7/8
Testdrive 7
Timed Out
Waited 1m 54s
·
Ran in 42m 45s
Agent
8/8
Testdrive 8
Timed Out
Waited 1m 57s
·
Ran in 42m 39s
Agent
1/4
Cluster tests 1
Waited 2m 8s
·
Ran in 23m 21s
Agent
2/4
Cluster tests 2
Timed Out
Waited 2m 13s
·
Ran in 34m 40s
Agent
3/4
Cluster tests 3
Timed Out
Waited 2m 16s
·
Ran in 35m 35s
Agent
4/4
Cluster tests 4
Timed Out
Waited 2m 14s
·
Ran in 34m 12s
Agent
1/6
Fast SQL logic tests 1
Timed Out
Waited 1m 55s
·
Ran in 31m 4s
Agent
2/6
Fast SQL logic tests 2
Timed Out
Waited 1m 59s
·
Ran in 31m 3s
Agent
3/6
Fast SQL logic tests 3
Timed Out
Waited 1m 59s
·
Ran in 30m 59s
Agent
4/6
Fast SQL logic tests 4
Timed Out
Waited 2m 4s
·
Ran in 30m 53s
Agent
5/6
Fast SQL logic tests 5
Timed Out
Waited 2m 5s
·
Ran in 30m 59s
Agent
6/6
Fast SQL logic tests 6
Timed Out
Waited 2m 1s
·
Ran in 30m 51s
Agent
Restart test
Timed Out
Waited 2m 14s
·
Ran in 30m 52s
Agent
1/2
Legacy upgrade tests (last version from docs, ignore missing) 1
Waited 10s
·
Ran in 29m 29s
Agent
2/2
Legacy upgrade tests (last version from docs, ignore missing) 2
Waited 2m 19s
·
Ran in 36m 47s
Agent
Debezium Postgres tests
Waited 2m 15s
·
Ran in 18m 37s
Agent
Debezium SQL Server tests
Timed Out
Waited 1m 56s
·
Ran in 35m 37s
Agent
Debezium MySQL tests
Waited 2m 14s
·
Ran in 18m 32s
Agent
1/2
MySQL CDC tests 1
Timed Out
Waited 2m 15s
·
Ran in 34m 16s
Agent
2/2
MySQL CDC tests 2
Timed Out
Waited 2m 18s
·
Ran in 35m 36s
Agent
1/6
MySQL CDC resumption tests 1
Waited 2m 18s
·
Ran in 13m 7s
Agent
2/6
MySQL CDC resumption tests 2
Timed Out
Waited 2m 21s
·
Ran in 35m 30s
Agent
3/6
MySQL CDC resumption tests 3
Waited 2m 21s
·
Ran in 20m 22s
Agent
4/6
MySQL CDC resumption tests 4
Waited 2m 16s
·
Ran in 26m 15s
Agent
5/6
MySQL CDC resumption tests 5
Waited 2m 19s
·
Ran in 29m 47s
Agent
6/6
MySQL CDC resumption tests 6
Waited 2m 16s
·
Ran in 24m 58s
Agent
MySQL RTR tests
Waited 2m 16s
·
Ran in 9m 43s
Agent
1/2
Postgres CDC tests 1
Timed Out
Waited 2m 19s
·
Ran in 35m 35s
Agent
2/2
Postgres CDC tests 2
Timed Out
Waited 2m 20s
·
Ran in 35m 33s
Agent
1/5
Postgres CDC resumption tests 1
Waited 2m 6s
·
Ran in 20m 5s
Agent
2/5
Postgres CDC resumption tests 2
Waited 2m 9s
·
Ran in 20m 21s
Agent
3/5
Postgres CDC resumption tests 3
Waited 2m 5s
·
Ran in 20m 12s
Agent
4/5
Postgres CDC resumption tests 4
Timed Out
Waited 2m 8s
·
Ran in 34m 32s
Agent
5/5
Postgres CDC resumption tests 5
Waited 2m 5s
·
Ran in 20m 41s
Agent
Postgres RTR tests
Waited 2m 20s
·
Ran in 10m 23s
Agent
Yugabyte CDC tests
Waited 2m 21s
·
Ran in 18m 25s
Agent
SQL Server CDC tests
Waited 1m 53s
·
Ran in 21m 39s
Agent
SSH connection tests
Waited 2m 21s
·
Ran in 14m 12s
Agent
Fivetran Destination tests
Waited 2m 21s
·
Ran in 8m 55s
Agent
Copy to S3
Waited 2m 27s
·
Ran in 14m 46s
Agent
Kafka resumption tests
Waited 2m 22s
·
Ran in 19m 21s
Agent
Kafka auth test
Waited 2m 23s
·
Ran in 15m 19s
Agent
Kafka exactly-once tests
Waited 2m 30s
·
Ran in 9m 43s
Agent
1/2
Kafka RTR tests 1
Waited 2m 29s
·
Ran in 13m 42s
Agent
2/2
Kafka RTR tests 2
Waited 2m 34s
·
Ran in 27m 28s
Agent
Short Zippy
Waited 2m 24s
·
Ran in 9m 11s
Agent
1/6
Checks + restart of environmentd & storage clusterd 1
Waited 2m 7s
·
Ran in 15m 18s
Agent
2/6
Checks + restart of environmentd & storage clusterd 2
Waited 2m 10s
·
Ran in 9m 4s
Agent
3/6
Checks + restart of environmentd & storage clusterd 3
Waited 2m 4s
·
Ran in 15m 39s
Agent
4/6
Checks + restart of environmentd & storage clusterd 4
Waited 2m 5s
·
Ran in 15m 12s
Agent
5/6
Checks + restart of environmentd & storage clusterd 5
Waited 2m 15s
·
Ran in 16m 12s
Agent
6/6
Checks + restart of environmentd & storage clusterd 6
Waited 2m 11s
·
Ran in 16m 26s
Agent
1/6
Checks without restart or upgrade 1
Waited 2m 10s
·
Ran in 14m 57s
Agent
2/6
Checks without restart or upgrade 2
Waited 2m 18s
·
Ran in 15m 56s
Agent
3/6
Checks without restart or upgrade 3
Waited 2m 15s
·
Ran in 9m 0s
Agent
4/6
Checks without restart or upgrade 4
Waited 2m 13s
·
Ran in 9m 18s
Agent
5/6
Checks without restart or upgrade 5
Waited 2m 13s
·
Ran in 16m 10s
Agent
6/6
Checks without restart or upgrade 6
Waited 3m 4s
·
Ran in 15m 13s
Agent
1/2
Source/Sink Error Reporting 1
Waited 2m 32s
·
Ran in 11m 29s
Agent
2/2
Source/Sink Error Reporting 2
Waited 2m 33s
·
Ran in 18m 11s
Agent
Feature benchmark (Kafka only)
Waited 1m 1s
·
Ran in 8m 42s
Agent
Persistence tests
Timed Out
Waited 2m 29s
·
Ran in 35m 25s
Agent
Cluster isolation test
Waited 2m 28s
·
Ran in 11m 50s
Agent
chbench smoke test
Waited 2m 34s
·
Ran in 14m 56s
Agent
Metabase smoke test
Timed Out
Waited 2m 13s
·
Ran in 35m 27s
Agent
dbt-materialize tests
Waited 2m 44s
·
Ran in 18m 7s
Agent
Storage Usage Table Test
Waited 2m 43s
·
Ran in 17m 58s
Agent
Tracing Fast Path
Waited 45s
·
Ran in 6m 18s
Agent
mz-debug tool
Timed Out
Waited 3m 17s
·
Ran in 32m 48s
Agent
Total Job Run Time: 1d 6h