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