Parent Log: http://ci.aztec-labs.com/95979217b3f59e6f Command: 2f76ae4bba915073 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/87c4b689268afecc86ab007c3587e45110daa43d Env: REF_NAME=gh-readonly-queue/next/pr-15220-282da3bd25d49b92970e6fc85f110092e8566299 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 16:35:00 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15220_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 16:35:03 [16:35:03.102] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:35:03 [16:35:03.645] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:35:04 [16:35:04.219] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 16:35:04 PASS src/synchronizer/synchronizer.test.ts 16:35:04 Synchronizer 16:35:04 ✓ sets header from latest block (551 ms) 16:35:04 ✓ removes notes from db on a reorg (671 ms) 16:35:04 16:35:04 Test Suites: 1 passed, 1 total 16:35:04 Tests: 2 passed, 2 total 16:35:04 Snapshots: 0 total 16:35:04 Time: 2.874 s 16:35:04 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 16:35:04 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?