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