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