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