Parent Log: http://ci.aztec-labs.com/16bd7f8bf151b42a Command: d2b17a71056754a7 yarn-project/scripts/run_test.sh stdlib/src/hash/hash.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/e1fded96333f986cee2b82440cf35579c6335754 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Mon Jun 16 23:20:26 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ea5bb2ff7a555cb0_next 23:20:29 PASS src/hash/hash.test.ts 23:20:29 hash 23:20:29 computes note hash nonce (270 ms) 23:20:29 computes unique note hash (3 ms) 23:20:29 computes siloed note hash (2 ms) 23:20:29 computes siloed nullifier (1 ms) 23:20:29 computes public data tree value (1 ms) 23:20:29 computes public data tree leaf slot (1 ms) 23:20:29 hashes empty function args (1 ms) 23:20:29 hashes function args (1 ms) 23:20:29 hashes many function args (9 ms) 23:20:29 compute secret message hash (2 ms) 23:20:29 Var args hash matches noir (5 ms) 23:20:29 L2ToL1Message siloing matches Noir (4 ms) 23:20:29 23:20:29 Test Suites: 1 passed, 1 total 23:20:29 Tests: 12 passed, 12 total 23:20:29 Snapshots: 12 passed, 12 total 23:20:29 Time: 1.793 s 23:20:29 Ran all test suites matching stdlib/src/hash/hash.test.ts. 23:20:29 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?