Parent Log:
http://ci.aztec-labs.com/a474c905046e6ed0
Command: 4d0fb449c606d482 yarn-project/scripts/run_test.sh pxe/src/storage/sync_data_provider/sync_data_provider.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/263498dd65e8700218979d7a94dbfd25b2a8a8a8
Env: REF_NAME=gh-readonly-queue/next/pr-14921-4b0e4dc09fa55f0bc808fa0c7c3e95e8fa997069 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Tue Jun 17 20:35:27 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14921_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next
20:35:29 [20:35:29.364]
INFO:
kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16
20:35:29 [20:35:29.416]
INFO:
kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16
20:35:29
PASS src/storage/sync_data_provider/sync_data_provider.test.ts
20:35:29 block header
20:35:29
✓ stores and retrieves the block header (57 ms)
20:35:29
✓ rejects getting header if no block set (34 ms)
20:35:29
20:35:29
Test Suites: 1 passed, 1 total
20:35:29
Tests: 2 passed, 2 total
20:35:29
Snapshots: 0 total
20:35:29
Time: 1.487 s
20:35:29
Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts
.
20:35:29
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?