Nightly

Public

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

wip

#10905
/
bkirwi:structured-on-disk-2/6e0af34978(#31080)
Canceled automatically after 53m 0s
:pipeline:
Ben Kirwin
Ben Kirwin
Created
Triggered from Web

Parallel Workload (DDL Only) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'tokio-runtime-worker' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(7 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-6' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_0 failed, exiting

HTTPConnectionPool(host='localhost', port=6976): Max retries exceeded with url: /api/sql (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xffff957df800>: Failed to establish a new connection: [Errno 111] Connection refused'))
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 --complexity=ddl-only --threads=2

Parallel Workload (kill) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'main' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-4' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(6 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-1' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(2 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-14' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(4 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-8' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(4 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-10' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(2 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-12' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-0' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(2 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-2' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-15' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(3 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-7' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-11' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(3 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-6' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-13' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'tokio:work-5' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(2 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-16' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_0 failed, exiting

('[Errno 104] Connection reset by peer', 'WS connect')
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=kill --threads=8

Parallel Workload (rename + naughty identifiers) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'tokio-runtime-worker' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(5 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-15' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

parallel-workload-materialized-1     | thread 'timely:work-0' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_0 failed, exiting

('Connection to remote host was lost.', 'DELETE FROM "db-pw-1737139487-0_%x(\'ls -al /\')"."s-0-32_<img src\\x32=x o"."t-4-21_0.0/0" WHERE true AND "c-0-text_File:///" = \'k7Q4sBYhRvC0JYGYsTa4BuZLOnbgWt7NMODw0d1R2u0Gmihkaz6AdVrW6MTZ3blZZBunnQ728aC9V6WQWFaukRkxhrXyspzBg4ij\' AND "c-1-int[]_0,0,0" = \'{53, -33, 26, -29, 10, 74, -27, -13, 11, -27, -83, 64, -41, -71, -40, 13, -79, 65, -53, 79}\'::int[] AND "c-2-timestamp_1.0/0.0" = TIMESTAMP \'55417-6-24\';')
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 --naughty-identifiers --threads=16

Parallel Workload (DDL) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'tokio-runtime-worker' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(5 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-4' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_0 failed, exiting

('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
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 --threads=8

Parallel Workload (rename) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'tokio-runtime-worker' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(3 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-13' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_0 failed, exiting

('consuming input failed: server closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.', "FETCH 349 c WITH (timeout='9s');")
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

Parallel Workload (DML) failed, main history: :bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed::bk-status-passed:

parallel-workload-materialized-1     | thread 'tokio-runtime-worker' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

(3 occurrences)

parallel-workload-materialized-1     | thread 'tokio:work-0' panicked at src/persist-client/src/fetch.rs:841:49: valid schemas for structured data

materialize.parallel_workload.worker_exception.WorkerFailedException: ^^^ +++ Thread worker_2 failed, exiting

('consuming input failed: server closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.', 'commit;')
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 --complexity=dml --threads=16
:pipeline:bin/ci-builder run stable bin/pyactivate -m ci.mkpipeline nightly "$@"
Waited 3s
·
Ran in 2m 7s
Agent
Parallel Workload (DML)
Waited 6m 36s
·
Ran in 6m 53s
Agent
Parallel Workload (DDL)
Waited 6m 39s
·
Ran in 9m 28s
Agent
Parallel Workload (DDL Only)
Waited 7m 30s
·
Ran in 30m 1s
Agent
Parallel Workload (rename + naughty identifiers)
Waited 7m 58s
·
Ran in 12m 30s
Agent
Parallel Workload (rename)
Waited 8m 23s
·
Ran in 6m 11s
Agent
Parallel Workload (kill)
Waited 8m 24s
·
Ran in 18m 44s
Agent
Parallel Workload (0dt deploy)
Canceled
Waited 49m 35s
·
Ran in 2m 9s
Agent
Total Job Run Time: 1h 28m