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