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