Parent Log:
http://ci.aztec-labs.com/5c36f3dacbf18e42
Command: 49f5129a0dc39cfa yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/4c695be4bff40a4a2ca2118c7e14c83a104e93aa
Env: REF_NAME=gh-readonly-queue/next/pr-15120-bbf33e6534f745d2f5a11c2f359583e881120fc4 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 17:22:56 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15120_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:22:58 [17:22:58.470]
INFO:
kv-store:lmdb-v2:test Starting data store with maxReaders 16
17:22:58 [17:22:58.963]
INFO:
kv-store:lmdb-v2:test Starting data store with maxReaders 16
17:22:59 [17:22:59.544]
WARN:
pxe:synchronizer Pruning data after block 3 due to reorg
17:22:59
PASS src/synchronizer/synchronizer.test.ts
17:22:59 Synchronizer
17:22:59
✓ sets header from latest block (501 ms)
17:22:59
✓ removes notes from db on a reorg (684 ms)
17:22:59
17:22:59
Test Suites: 1 passed, 1 total
17:22:59
Tests: 2 passed, 2 total
17:22:59
Snapshots: 0 total
17:22:59
Time: 2.66 s
17:22:59
Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts
.
17:22:59
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?