Parent Log: http://ci.aztec-labs.com/f200125a56fdc063 Command: ca6d19ec133d445c yarn-project/scripts/run_test.sh sequencer-client/src/sequencer/timetable.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/99e234fe4473771b32124e0402885610a6a3f98a Env: REF_NAME=gh-readonly-queue/next/pr-15233-1c9ca312bfdace816082212846900a49694e1e50 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 24 09:09:42 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15233_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:09:44 PASS src/sequencer/timetable.test.ts 09:09:44 sequencer-timetable 09:09:44 constructor 09:09:44 ✓ fails to construct an instance with too short slot duration (13 ms) 09:09:44 ✓ allows a slot duration of at least two ethereum slots (1 ms) 09:09:44 maxAllowedTime 09:09:44 ✓ computes time from slot start 09:09:44 ✓ computes time from slot end 09:09:44 ✓ returns an increasing time for each stage (1 ms) 09:09:44 assertTimeLeft 09:09:44 ✓ throws if time is up (1 ms) 09:09:44 ✓ does not throw if enough time left 09:09:44 ✓ handles negative seconds into slot 09:09:44 ✓ skips check if enforcement is off 09:09:44 getBlockProposalExecTimeEnd 09:09:44 ✓ sets deadline considering unused time from init phase 09:09:44 ✓ sets deadline considering starting before slot (1 ms) 09:09:44 ✓ sets deadline when building on time 09:09:44 ✓ sets deadline before current time if too late 09:09:44 getValidatorReexecTimeEnd 09:09:44 ✓ sets deadline 09:09:44 ✓ sets time available equal to block building 09:09:44 09:09:44 Test Suites: 1 passed, 1 total 09:09:44 Tests: 15 passed, 15 total 09:09:44 Snapshots: 0 total 09:09:44 Time: 1.216 s 09:09:44 Ran all test suites matching sequencer-client/src/sequencer/timetable.test.ts. 09:09:44 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?