Parent Log:
http://ci.aztec-labs.com/da2e9aeec7681664
Command: a8cc061dbe484831 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/107a625e4a5b124b87c02fa9ff2ae12b5778baa9
Env: REF_NAME=gh-readonly-queue/next/pr-15186-54fc27adbce52a5aa04aeae6eec34ae4b1044f92 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 20 14:24:20 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15186_amd64_x3-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next
14:24:22 [14:24:22.775]
INFO:
kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16
14:24:22 [14:24:22.814]
INFO:
kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16
14:24:22
PASS src/storage/sync_data_provider/sync_data_provider.test.ts
14:24:22 block header
14:24:22
✓ stores and retrieves the block header (58 ms)
14:24:22
✓ rejects getting header if no block set (26 ms)
14:24:22
14:24:22
Test Suites: 1 passed, 1 total
14:24:22
Tests: 2 passed, 2 total
14:24:22
Snapshots: 0 total
14:24:22
Time: 1.552 s
14:24:22
Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts
.
14:24:22
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?