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