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