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