Parent Log: http://ci.aztec-labs.com/1b3bcb5ac1be61c4 Command: e080141c28855ec1 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/ef6780e77e5f82f98ddfe92fd387cfd5fa7682e8 Env: REF_NAME=gh-readonly-queue/next/pr-15014-80d800435dd8dfa325e38593d83b405488449dba CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 16:00:55 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15014_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_a1bb86cff1c0cde7_next 16:00:58 [16:00:58.140] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 16:00:59 [16:00:59.393] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 16:00:59 [16:00:59.435] INFO: kv-store:lmdb-v2:contract_data_provider_test Starting data store with maxReaders 16 16:00:59 PASS src/storage/contract_data_provider/contract_data_provider.test.ts 16:00:59 ContractDataProvider 16:00:59 stores a contract artifact (1276 ms) 16:00:59 does not store a contract artifact with a duplicate private function selector (42 ms) 16:00:59 stores a contract instance (31 ms) 16:00:59 16:00:59 Test Suites: 1 passed, 1 total 16:00:59 Tests: 3 passed, 3 total 16:00:59 Snapshots: 0 total 16:00:59 Time: 2.925 s 16:00:59 Ran all test suites matching pxe/src/storage/contract_data_provider/contract_data_provider.test.ts. 16:00:59 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?