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