Nightly
PublicTests that are too slow or non-deterministic for the regular Test pipeline
Scheduled build
Failed in 5h 45m
Miri test (full)
blob storeParallel 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-04-01T23:50:21.260147Z thread 'coordinator' panicked at src/storage-controller/src/lib.rs:973:17: dependency since has advanced past dependent (u143) 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
SQLsmith explain failed, main history:
sqlsmith-mz_2-1 | 2025-04-01T23:45:28.358197Z thread 'tokio:work-12' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Date(Date { days: 8401 })
sqlsmith-mz_1-1 | 2025-04-01T23:46:36.776496Z thread 'tokio:work-6' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
sqlsmith-mz_2-1 | 2025-04-01T23:47:53.630281Z thread 'tokio:work-6' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Int32(95)
sqlsmith-mz_2-1 | 2025-04-01T23:52:19.296267Z thread 'tokio:work-29' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Int32(2228224)
sqlsmith-mz_2-1 | 2025-04-01T23:55:43.309235Z thread 'tokio:work-3' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Int32(-2)
sqlsmith-mz_2-1 | 2025-04-01T23:56:49.678537Z thread 'tokio:work-13' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on UInt64(18446744073709551615)
sqlsmith-mz_2-1 | 2025-04-01T23:58:24.460612Z thread 'tokio:work-21' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
sqlsmith-mz_1-1 | 2025-04-01T23:58:35.543363Z thread 'tokio:work-21' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on UInt32(0)
sqlsmith-mz_2-1 | 2025-04-01T23:58:48.838563Z thread 'tokio:work-14' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Range(Range { inner: Some(RangeInner { lower: RangeBound { inclusive: false, bound: None }, upper: RangeBound { inclusive: false, bound: Some(DatumNested { val: Int64(9223372036854775807) }) } }) })
sqlsmith-mz_2-1 | 2025-04-02T00:02:39.911788Z thread 'coordinator' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Float64(-2.0)
sqlsmith-mz_1-1 | 2025-04-02T00:03:20.298347Z thread 'tokio:work-22' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Int32(4)
sqlsmith-mz_2-1 | 2025-04-02T00:07:04.516710Z thread 'tokio:work-10' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
sqlsmith-mz_2-1 | 2025-04-02T00:07:30.057546Z thread 'tokio:work-0' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
Test details & reproducer
Use SQLsmith to generate random queries (AST/code based) and run them against Materialize: https://github.com/MaterializeInc/sqlsmith The queries can be complex, but we can't verify correctness or performance.bin/mzcompose --find sqlsmith run default --max-joins=15 --explain-only --runtime=1500
SQLsmith failed, main history:
sqlsmith-mz_2-1 | 2025-04-01T23:48:46.932081Z thread 'tokio:work-3' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
sqlsmith-mz_2-1 | 2025-04-01T23:51:06.873516Z thread 'tokio:work-0' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Bytes([110, 52, 11, 156, 255, 179, 122, 152, 156, 165, 68, 230, 187, 120, 10, 44, 120, 144, 29, 63, 179, 55, 56, 118, 133, 17, 163, 6, 23, 175, 160, 29])
sqlsmith-mz_1-1 | 2025-04-01T23:51:14.087567Z thread 'tokio:work-0' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on Date(Date { days: 8401 })
sqlsmith-mz_2-1 | 2025-04-02T00:04:11.609728Z thread 'tokio:work-0' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on False
sqlsmith-mz_2-1 | 2025-04-02T00:08:19.042898Z thread 'tokio:work-0' panicked at src/expr/src/scalar/func.rs:2154:31: Datum::unwrap_string called on True
Test details & reproducer
Use SQLsmith to generate random queries (AST/code based) and run them against Materialize: https://github.com/MaterializeInc/sqlsmith The queries can be complex, but we can't verify correctness or performance.bin/mzcompose --find sqlsmith run default --max-joins=2 --runtime=1500
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