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