Parent Log: http://ci.aztec-labs.com/bc4ab70457179ef3 Command: 7c288cdaeed3e186 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/58b067708e8ff927bf26b2994203134853a7eb71 Env: REF_NAME=gh-readonly-queue/next/pr-15078-3b44f825dcd3249b2c8a1105905fa3394aa7213d CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 17:52:52 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15078_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 17:52:54 [17:52:54.726] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:52:55 [17:52:55.301] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:52:55 [17:52:55.865] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 17:52:56 PASS src/synchronizer/synchronizer.test.ts 17:52:56 Synchronizer 17:52:56 ✓ sets header from latest block (596 ms) 17:52:56 ✓ removes notes from db on a reorg (699 ms) 17:52:56 17:52:56 Test Suites: 1 passed, 1 total 17:52:56 Tests: 2 passed, 2 total 17:52:56 Snapshots: 0 total 17:52:56 Time: 2.899 s 17:52:56 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 17:52:56 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?