Parent Log:
http://ci.aztec-labs.com/f148a4758ed7d751
Command: bbc5a7ea91d19a83 yarn-project/scripts/run_test.sh stdlib/src/contract/utility_function_membership_proof.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/4800d08570523bc1b2a9e8ec0dfb09e326f4689a
Env: REF_NAME=gh-readonly-queue/next/pr-14900-d3bba2d69dbc070d51bcd50607354193573876ba CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 13 13:32:34 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14900_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_c9bb7c25acd58654_next
13:32:38
PASS src/contract/utility_function_membership_proof.test.ts
13:32:38 utility_function_membership_proof
13:32:38
✓ computes and verifies a proof (693 ms)
13:32:38
✓ handles a contract with a single function (482 ms)
13:32:38
✓ fails proof if artifactTreeSiblingPath is mangled (345 ms)
13:32:38
✓ fails proof if artifactMetadataHash is mangled (336 ms)
13:32:38
✓ fails proof if functionMetadataHash is mangled (311 ms)
13:32:38
13:32:38
Test Suites: 1 passed, 1 total
13:32:38
Tests: 5 passed, 5 total
13:32:38
Snapshots: 0 total
13:32:38
Time: 2.899 s
13:32:38
Ran all test suites matching /stdlib\/src\/contract\/utility_function_membership_proof.test.ts/i
.
13:32:38
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?