Parent Log: http://ci.aztec-labs.com/2b73bd385831a8d5 Command: a8cc061dbe484831 yarn-project/scripts/run_test.sh sequencer-client/src/sequencer/timetable.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/107a625e4a5b124b87c02fa9ff2ae12b5778baa9 Env: REF_NAME=gh-readonly-queue/next/pr-15186-54fc27adbce52a5aa04aeae6eec34ae4b1044f92 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 14:25:05 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15186_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_820487f8760c5450_next 14:25:07 PASS src/sequencer/timetable.test.ts 14:25:07 sequencer-timetable 14:25:07 constructor 14:25:07 fails to construct an instance with too short slot duration (17 ms) 14:25:07 allows a slot duration of at least two ethereum slots (1 ms) 14:25:07 maxAllowedTime 14:25:07 computes time from slot start 14:25:07 computes time from slot end (1 ms) 14:25:07 returns an increasing time for each stage (1 ms) 14:25:07 assertTimeLeft 14:25:07 throws if time is up (1 ms) 14:25:07 does not throw if enough time left 14:25:07 handles negative seconds into slot 14:25:07 skips check if enforcement is off (1 ms) 14:25:07 getBlockProposalExecTimeEnd 14:25:07 sets deadline considering unused time from init phase 14:25:07 sets deadline considering starting before slot 14:25:07 sets deadline when building on time (1 ms) 14:25:07 sets deadline before current time if too late 14:25:07 getValidatorReexecTimeEnd 14:25:07 sets deadline (1 ms) 14:25:07 sets time available equal to block building 14:25:07 14:25:07 Test Suites: 1 passed, 1 total 14:25:07 Tests: 15 passed, 15 total 14:25:07 Snapshots: 0 total 14:25:07 Time: 1.629 s 14:25:07 Ran all test suites matching sequencer-client/src/sequencer/timetable.test.ts. 14:25:07 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?