Parent Log: http://ci.aztec-labs.com/5209a44cea503853 Command: b54d5ade67e7ffc9 yarn-project/scripts/run_test.sh stdlib/src/hash/hash.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/347f29fb98cc855ead57129b4d1a444d9fb16820 Env: REF_NAME=gh-readonly-queue/next/pr-15059-16fc84676c7308fa5f7ca4a54b67319803d0f5b7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:00:53 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15059_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ea5bb2ff7a555cb0_next 16:00:56 PASS src/hash/hash.test.ts 16:00:56 hash 16:00:56 computes note hash nonce (281 ms) 16:00:56 computes unique note hash (2 ms) 16:00:56 computes siloed note hash (2 ms) 16:00:56 computes siloed nullifier (1 ms) 16:00:56 computes public data tree value 16:00:56 computes public data tree leaf slot (1 ms) 16:00:56 hashes empty function args (4 ms) 16:00:56 hashes function args (1 ms) 16:00:56 hashes many function args (11 ms) 16:00:56 compute secret message hash (1 ms) 16:00:56 Var args hash matches noir (5 ms) 16:00:56 L2ToL1Message siloing matches Noir (4 ms) 16:00:56 16:00:56 Test Suites: 1 passed, 1 total 16:00:56 Tests: 12 passed, 12 total 16:00:56 Snapshots: 12 passed, 12 total 16:00:56 Time: 2.154 s 16:00:56 Ran all test suites matching stdlib/src/hash/hash.test.ts. 16:00:56 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?