Parent Log: http://ci.aztec-labs.com/a3bb03fa16e317bc Command: 00c2c16648004337 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/015cb0cadef6a41094c3649f32a735392e1b9693 Env: REF_NAME=gh-readonly-queue/master/pr-15027-e9a2301883801edbe36ea8bba05dcca7e714f30a CURRENT_VERSION=0.87.8 CI_FULL=0 Date: Wed Jun 18 14:28:37 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15027_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_master 14:28:39 [14:28:39.495] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:28:39 [14:28:39.853] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:28:40 [14:28:40.401] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 14:28:40 PASS src/synchronizer/synchronizer.test.ts 14:28:40 Synchronizer 14:28:40 sets header from latest block (356 ms) 14:28:40 removes notes from db on a reorg (646 ms) 14:28:40 14:28:40 Test Suites: 1 passed, 1 total 14:28:40 Tests: 2 passed, 2 total 14:28:40 Snapshots: 0 total 14:28:40 Time: 1.992 s 14:28:40 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 14:28:40 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?