Parent Log: http://ci.aztec-labs.com/d9cbe39da05505e1 Command: f682b45a820409ef yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/c0e766a133071c44b2c0d8fac5df352c6e059df1 Env: REF_NAME=gh-readonly-queue/next/pr-15015-cf8be0f9e81e248048560619de041e90d9d6990a CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 07:56:07 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15015_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 07:56:10 [07:56:10.297] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 07:56:10 [07:56:10.686] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 07:56:11 [07:56:11.158] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 07:56:11 PASS src/synchronizer/synchronizer.test.ts 07:56:11 Synchronizer 07:56:11 ✓ sets header from latest block (388 ms) 07:56:11 ✓ removes notes from db on a reorg (556 ms) 07:56:11 07:56:11 Test Suites: 1 passed, 1 total 07:56:11 Tests: 2 passed, 2 total 07:56:11 Snapshots: 0 total 07:56:11 Time: 2.351 s 07:56:11 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 07:56:11 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?