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