Parent Log: http://ci.aztec-labs.com/1c420a977384450c Command: 426cee6a32f1da3c yarn-project/scripts/run_test.sh stdlib/src/contract/utility_function_membership_proof.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d96baf1c44329e8b2e3a432ad803f702f5184a62 Env: REF_NAME=gh-readonly-queue/next/pr-15025-26c5a39fe03723d11540f721293d7aebd1f478d9 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 09:33:38 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15025_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c9bb7c25acd58654_next 09:33:42 PASS src/contract/utility_function_membership_proof.test.ts 09:33:42 utility_function_membership_proof 09:33:42 ✓ computes and verifies a proof (675 ms) 09:33:42 ✓ handles a contract with a single function (467 ms) 09:33:42 ✓ fails proof if artifactTreeSiblingPath is mangled (315 ms) 09:33:42 ✓ fails proof if artifactMetadataHash is mangled (310 ms) 09:33:42 ✓ fails proof if functionMetadataHash is mangled (303 ms) 09:33:42 09:33:42 Test Suites: 1 passed, 1 total 09:33:42 Tests: 5 passed, 5 total 09:33:42 Snapshots: 0 total 09:33:42 Time: 2.751 s 09:33:42 Ran all test suites matching /stdlib\/src\/contract\/utility_function_membership_proof.test.ts/i. 09:33:42 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?