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