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