Parent Log: http://ci.aztec-labs.com/c1f491862c605f23 Command: 6db87052395d3483 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/41cc1f518fed92110a82ce3c59385a3f5c0d8817 Env: REF_NAME=gh-readonly-queue/next/pr-15041-9cf4a24266245fa3ca003adb00e8ae759880c107 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 17:16:02 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15041_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 17:16:05 [17:16:05.702] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:16:06 [17:16:06.245] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:16:06 [17:16:06.832] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 17:16:06 PASS src/synchronizer/synchronizer.test.ts 17:16:06 Synchronizer 17:16:06 ✓ sets header from latest block (566 ms) 17:16:06 ✓ removes notes from db on a reorg (711 ms) 17:16:06 17:16:06 Test Suites: 1 passed, 1 total 17:16:06 Tests: 2 passed, 2 total 17:16:06 Snapshots: 0 total 17:16:06 Time: 3.051 s 17:16:06 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 17:16:06 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?