Nightly
PublicTests that are too slow or non-deterministic for the regular Test pipeline
Scheduled build
Failed in 7h 35m
Canary Deploy in Staging Cloud (#2) failed, main history:
- Unknown error in workflow-default:
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
Scalability benchmark (read & write) against merge base or 'latest' failed, main history:
- Unknown error in Workload 'SelectLimitWorkload':
New regression against v0.139.1 (b670dba46)
Regression in workload 'SelectLimitWorkload' at concurrency 2 with MaterializeContainer (None specified as HEAD): 583.98 tps vs. 823.85 tps (-239.87 tps; -29.12%)
Test details & reproducer
Benchmark for how various queries scale, compares against old Materialize versions.bin/mzcompose --find scalability run default --target HEAD --target common-ancestor --regression-against common-ancestor --workload-group-marker DmlDqlWorkload --max-concurrency 256
Parallel Workload (0dt deploy) succeeded with known error logs, main history: 




- Known issue parallel-workload: 0dt: thread 'coordinator' panicked at src/storage-controller/src/lib.rs:703:17: dependency since has advanced past dependent (u417) upper (#8425) in services.log:
parallel-workload-materialized2-1 | 2025-03-29T00:22:04.862028Z thread 'coordinator' panicked at src/storage-controller/src/lib.rs:973:17: dependency since has advanced past dependent (u438) upper
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=0dt-deploy --threads=16
Checks 0dt upgrade across two versions 1 succeeded with known error logs, main history: 




- Known issue parallel-workload: 0dt: thread 'coordinator' panicked at src/storage-controller/src/lib.rs:703:17: dependency since has advanced past dependent (u417) upper (#8425) in services.log:
platform-checks-mz_4-1 | 2025-03-28T23:57:28.801991Z thread 'coordinator' panicked at src/storage-controller/src/lib.rs:973:17: dependency since has advanced past dependent (u492) 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.BUILDKITE_PARALLEL_JOB=0 BUILDKITE_PARALLEL_JOB_COUNT=2 bin/mzcompose --find platform-checks run default --scenario=ZeroDowntimeUpgradeEntireMzTwoVersions --seed=0195df17-56db-4bf2-a01f-7f28bf9ad6d6
Canary Deploy in Staging Cloud failed, main history:
- Unknown error in workflow-default:
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
Total Job Run Time: 6d 3h