Nightly

Public

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

Scheduled build

Failed in 6h 40m
: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
Checks 0dt upgrade to a bumped version succeeded with known error logs, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:
platform-checks-mz_3-1              | 2025-03-30T00:19:14.892662Z  thread 'coordinator' panicked at src/storage-controller/src/lib.rs:973:17: dependency since has advanced past dependent (u886) upper 
Test details & reproducer Write a single set of .td fragments for a particular feature or functionality and then have Zippy execute them in upgrade, 0dt-upgrade, restart, recovery and failure contexts.
bin/mzcompose --find platform-checks run default --scenario=ZeroDowntimeBumpedVersion --seed=0195e43d-b196-46c8-9488-e0ce22315b3c 

Parallel Workload (rename) with :azure: blob store failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

Mar 30 00:14:22 hetzner-aarch64-16cpu-32gb-f80312a5 kernel: Memory cgroup out of memory: Killed process 31796 (clusterd) total-vm:31494208kB, anon-rss:11609180kB, file-rss:111992kB, shmem-rss:0kB, UID:999 pgtables:53764kB oom_score_adj:0
Mar 30 00:14:23 hetzner-aarch64-16cpu-32gb-f80312a5 kernel: Memory cgroup out of memory: Killed process 31793 (clusterd) total-vm:27527872kB, anon-rss:12719384kB, file-rss:112204kB, shmem-rss:0kB, UID:999 pgtables:46388kB oom_score_adj:0
Test details & reproducer Runs a randomized parallel workload stressing all parts of Materialize, can mostly find panics and unexpected errors. See zippy for a sequential randomized tests which can verify correctness.
bin/mzcompose --find parallel-workload run default --runtime=1500 --scenario=rename --threads=16 --azurite 

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

builtins.ValueError: Redpanda API call failed: 400 {"code":"INVALID_ARGUMENT", "message":"throughput tier tier-1-aws-v2-arm is not available in region us-east-1 for cluster type TYPE_DEDICATED", "details":[{"@type":"google.rpc.ErrorInfo", "reason":"REASON_THROUGHPUT_TIER_NOT_AVAILABLE_IN_REGION", "domain":"redpanda.com/controlplane", "metadata":{"cluster_type":"TYPE_DEDICATED", "region":"us-east-1", "throughput_tier_name":"tier-1-aws-v2-arm"}}]}
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 
Canary Deploy in Staging Cloud
Waited 54s
·
Ran in 23m 30s
Total Job Run Time: 6d 0h