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