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