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