Nightly
PublicTests that are too slow or non-deterministic for the regular Test pipeline
Relax remaining offset check. Negative numbers are acceptable
Failed in 2h 52m
Miri test (full)
Triggered from Web
Checks 0dt upgrade across two versions succeeded with known error logs, main history: 
- Known issue unexpected lease expiry 'ReaderId/WriterId was expired due to inactivity.' (#8514) in services.log:
platform-checks-mz_4-1 | thread 'timely:work-0' panicked at src/persist-client/src/internal/state.rs:1540:17: LeasedReaderId(r8d07eed2-3466-4186-b706-30134152472d) was expired due to inactivity. Did the machine go to sleep?
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=ZeroDowntimeUpgradeEntireMzTwoVersions --seed=0192c4f1-b6e4-40ed-acc1-33ae44f23087
Checks 0dt restart of the entire Mz with forced migrations succeeded with known error logs, main history:
- Known issue unexpected lease expiry 'ReaderId/WriterId was expired due to inactivity.' (#8514) in services.log:
platform-checks-mz_4-1 | thread 'timely:work-3' panicked at src/persist-client/src/internal/state.rs:1540:17: LeasedReaderId(r1dd9e145-b423-4e17-9e7e-c3e99cd98498) was expired due to inactivity. Did the machine go to sleep?
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=ZeroDowntimeRestartEntireMzForcedMigrations --seed=0192c4f1-b6e4-40ed-acc1-33ae44f23087
Detect references to already closed issuesbin/ci-builder run stable bin/ci-closed-issues-detect
Waited 8s
Ran in 3m 52s
Total Job Run Time: 3d 10h