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