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