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