Parent Log: http://ci.aztec-labs.com/83b16f57969d44fb Command: 71ec8227227d28e6 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/a45107e7f95b675cb2768b6bcb06483b511141f4 Env: REF_NAME=gh-readonly-queue/next/pr-15018-2731d9a8aebf63d05db1a786296abdf897c49490 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Thu Jun 12 17:44:58 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15018_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 17:45:01 [17:45:01.325] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:45:01 [17:45:01.826] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:45:02 [17:45:02.417] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 17:45:02 PASS src/synchronizer/synchronizer.test.ts 17:45:02 Synchronizer 17:45:02 ✓ sets header from latest block (502 ms) 17:45:02 ✓ removes notes from db on a reorg (709 ms) 17:45:02 17:45:02 Test Suites: 1 passed, 1 total 17:45:02 Tests: 2 passed, 2 total 17:45:02 Snapshots: 0 total 17:45:02 Time: 2.761 s 17:45:02 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 17:45:02 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?