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