Parent Log: http://ci.aztec-labs.com/a6ad5c00f5faa201 Command: 4a8fdb7487b9ad73 yarn-project/scripts/run_test.sh stdlib/src/contract/utility_function_membership_proof.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/420e0a54fb4bfe8b04d7dd479f59ed0fe3ad3b74 Env: REF_NAME=gh-readonly-queue/next/pr-14922-106f897363bb5aee27ddd091b5be9641b011c5bb CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 16:15:40 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14922_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_c9bb7c25acd58654_next 16:15:43 PASS src/contract/utility_function_membership_proof.test.ts 16:15:43 utility_function_membership_proof 16:15:43 ✓ computes and verifies a proof (529 ms) 16:15:43 ✓ handles a contract with a single function (423 ms) 16:15:43 ✓ fails proof if artifactTreeSiblingPath is mangled (283 ms) 16:15:43 ✓ fails proof if artifactMetadataHash is mangled (276 ms) 16:15:43 ✓ fails proof if functionMetadataHash is mangled (282 ms) 16:15:43 16:15:43 Test Suites: 1 passed, 1 total 16:15:43 Tests: 5 passed, 5 total 16:15:43 Snapshots: 0 total 16:15:43 Time: 2.265 s 16:15:43 Ran all test suites matching /stdlib\/src\/contract\/utility_function_membership_proof.test.ts/i. 16:15:43 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?