Parent Log: http://ci.aztec-labs.com/bb5a5dfbdc7368c1 Command: a5511b51e55ea9c0 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/0dc6f60f84deaa57a8570f9942eb75317f5aeea5 Env: REF_NAME=gh-readonly-queue/next/pr-15162-6ee95286f8bcc5bb6dca43222459ac5bf43a8a75 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 09:43:03 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15162_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 09:43:06 [09:43:06.018] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 09:43:06 [09:43:06.531] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 09:43:07 [09:43:07.148] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 09:43:07 PASS src/synchronizer/synchronizer.test.ts 09:43:07 Synchronizer 09:43:07 ✓ sets header from latest block (525 ms) 09:43:07 ✓ removes notes from db on a reorg (732 ms) 09:43:07 09:43:07 Test Suites: 1 passed, 1 total 09:43:07 Tests: 2 passed, 2 total 09:43:07 Snapshots: 0 total 09:43:07 Time: 2.964 s 09:43:07 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 09:43:07 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?