Nightly

Public

Tests that are too slow or non-deterministic for the regular Test pipeline

Scheduled build

Failed in 5h 49m
:pipeline:
:rust: Miri test (full)
Extended SSH connection tests
CRDB rolling restarts
PubSub disruption
Test for incident 70
Tests for balancerd
CRDB / Persist backup and restore
Postgres / Persist backup and restore
Replica isolation
Zero downtime
Materialize Emulator
Cluster tests with :azure: blob store

Feature benchmark against merge base or 'latest' 2 failed, main history: :bk-status-failed::bk-status-failed::bk-status-failed::bk-status-failed::bk-status-passed:

New regression against v0.141.2
NAME                                | TYPE            |      THIS       |      OTHER      |  UNIT  | THRESHOLD  |  Regression?  | 'THIS' is
--------------------------------------------------------------------------------------------------------------------------------------------------------
ManyKafkaSourcesOnSameCluster       | wallclock       |          27.570 |          27.482 |   s    |    10%     |      no       | worse:   0.3% slower
ManyKafkaSourcesOnSameCluster       | memory_mz       |        2527.237 |        2600.670 |   MB   |    20%     |      no       | better:  2.8% less
ManyKafkaSourcesOnSameCluster       | memory_clusterd |          70.601 |          31.996 |   MB   |    50%     |    !!YES!!    | worse:   2.2 TIMES more
Test details & reproducer Simple benchmark of mostly individual queries using testdrive. Can find wallclock/memorys regressions in single-connection query executions, not suitable for concurrency.
BUILDKITE_PARALLEL_JOB=1 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find feature-benchmark run default --other-tag common-ancestor 

Feature benchmark against merge base or 'latest' 6 failed, main history: :bk-status-failed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

New regression against v0.141.2
NAME                                | TYPE            |      THIS       |      OTHER      |  UNIT  | THRESHOLD  |  Regression?  | 'THIS' is
--------------------------------------------------------------------------------------------------------------------------------------------------------
PgCdcInitialLoad                    | wallclock       |           1.324 |           1.170 |   s    |    10%     |    !!YES!!    | worse:  13.2% slower
PgCdcInitialLoad                    | memory_mz       |         781.059 |         774.956 |   MB   |    20%     |      no       | worse:   0.8% more
PgCdcInitialLoad                    | memory_clusterd |          64.287 |          62.876 |   MB   |    50%     |      no       | worse:   2.2% more
Test details & reproducer Simple benchmark of mostly individual queries using testdrive. Can find wallclock/memorys regressions in single-connection query executions, not suitable for concurrency.
BUILDKITE_PARALLEL_JOB=5 BUILDKITE_PARALLEL_JOB_COUNT=8 bin/mzcompose --find feature-benchmark run default --other-tag common-ancestor 

Canary Deploy in Staging Cloud failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-failed:

builtins.ValueError: Redpanda API call failed: 404 {"code":"NOT_FOUND","message":"","details":[]}
Test details & reproducer Deploy the current version on a real Staging Cloud, and run some basic verifications, like ingesting data from Kafka and Redpanda Cloud using AWS Privatelink. Runs only on main and release branches.
bin/mzcompose --find cloud-canary run default 

Terraform + Helm Chart E2E on AWS failed, main history: :bk-status-passed::bk-status-passed::bk-status-failed::bk-status-failed::bk-status-failed:

[31mERROR[0m mz-debug: fatal: No SQL port forwarding info found. Set --auto-port-forward to false and point --mz-connection-url to a Materialize instance.
builtins.ValueError: Never completed
Test details & reproducer Tests the mz command line tool against a real Cloud instance
bin/mzcompose --find terraform run aws-temporary 

Terraform + Helm Chart E2E on GCP failed, main history: :bk-status-passed::bk-status-passed::bk-status-failed::bk-status-failed::bk-status-failed:

environmentd: fatal: --license-key is required when running in Kubernetes
[31mERROR[0m mz-debug: fatal: No SQL port forwarding info found. Set --auto-port-forward to false and point --mz-connection-url to a Materialize instance.
builtins.ValueError: Never completed
Test details & reproducer Tests the mz command line tool against a real Cloud instance
bin/mzcompose --find terraform run gcp-temporary 

Terraform + Helm Chart E2E on Azure failed, main history: :bk-status-passed::bk-status-passed::bk-status-failed::bk-status-failed::bk-status-failed:

[31mERROR[0m mz-debug: fatal: No SQL port forwarding info found. Set --auto-port-forward to false and point --mz-connection-url to a Materialize instance.
builtins.ValueError: Never completed
Test details & reproducer Tests the mz command line tool against a real Cloud instance
bin/mzcompose --find terraform run azure-temporary 
2/8
Feature benchmark against merge base or 'latest' 2
Waited 1m 5s
·
Ran in 5h 46m
6/8
Feature benchmark against merge base or 'latest' 6
Waited 2m 39s
·
Ran in 2h 11m
Platform checks upgrade in Cloudtest/K8s
Timed Out
Waited 49s
·
Ran in 4h 4m
Canary Deploy in Staging Cloud
Waited 49s
·
Ran in 1h 22m
Terraform + Helm Chart E2E on AWS
Waited 49s
·
Ran in 49m 22s
Terraform + Helm Chart E2E on GCP
Waited 50s
·
Ran in 48m 10s
Terraform + Helm Chart E2E on Azure
Waited 53s
·
Ran in 46m 43s
Total Job Run Time: 5d 20h