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