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