Parent Log:
http://ci.aztec-labs.com/9dbdeae6fbc98ad5
Command: d14a91e37c8b1083 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/97080f178c0a3e244c64b3c17bf255bed63fc3cf
Env: REF_NAME=gh-readonly-queue/next/pr-15065-4110b08ca823c6af4399e58e54e0483d6e3459ed CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Mon Jun 16 10:22:40 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15065_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next
10:22:42 [10:22:42.464]
INFO:
kv-store:lmdb-v2:test Starting data store with maxReaders 16
10:22:42 [10:22:42.905]
INFO:
kv-store:lmdb-v2:test Starting data store with maxReaders 16
10:22:43 [10:22:43.545]
WARN:
pxe:synchronizer Pruning data after block 3 due to reorg
10:22:43
PASS src/synchronizer/synchronizer.test.ts
10:22:43 Synchronizer
10:22:43
✓ sets header from latest block (442 ms)
10:22:43
✓ removes notes from db on a reorg (739 ms)
10:22:43
10:22:43
Test Suites: 1 passed, 1 total
10:22:43
Tests: 2 passed, 2 total
10:22:43
Snapshots: 0 total
10:22:43
Time: 2.702 s
10:22:43
Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i
.
10:22:43
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?