Parent Log: http://ci.aztec-labs.com/ab63b2ef1085df0f Command: 68e9475192d7aeac yarn-project/scripts/run_test.sh pxe/src/storage/contract_data_provider/contract_data_provider.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/fe25e8151d865a744220512c782713e46482165a Env: REF_NAME=next CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Sat Jun 21 10:22:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a1bb86cff1c0cde7_staging 10:22:30 [10:22:30.268] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 10:22:31 [10:22:31.473] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 10:22:31 [10:22:31.512] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 10:22:31 PASS src/storage/contract_data_provider/contract_data_provider.test.ts 10:22:31 ContractDataProvider 10:22:31 ✓ stores a contract artifact (1214 ms) 10:22:31 ✓ does not store a contract artifact with a duplicate private function selector (42 ms) 10:22:31 ✓ stores a contract instance (30 ms) 10:22:31 10:22:31 Test Suites: 1 passed, 1 total 10:22:31 Tests: 3 passed, 3 total 10:22:31 Snapshots: 0 total 10:22:31 Time: 2.574 s 10:22:31 Ran all test suites matching pxe/src/storage/contract_data_provider/contract_data_provider.test.ts. 10:22:31 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?