Parent Log: http://ci.aztec-labs.com/96c46d3891517db0 Command: 1c06fcdf9304d11a yarn-project/scripts/run_test.sh stdlib/src/hash/hash.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1b899817816052aa86b702e2fe099b5054167aa3 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Wed Jun 18 21:26:57 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 21:26:59 PASS src/hash/hash.test.ts 21:26:59 hash 21:26:59 computes note hash nonce (240 ms) 21:26:59 computes unique note hash (3 ms) 21:26:59 computes siloed note hash (2 ms) 21:26:59 computes siloed nullifier (2 ms) 21:26:59 computes public data tree value (1 ms) 21:26:59 computes public data tree leaf slot (2 ms) 21:26:59 hashes empty function args (1 ms) 21:26:59 hashes function args (1 ms) 21:26:59 hashes many function args (8 ms) 21:26:59 compute secret message hash (1 ms) 21:26:59 Var args hash matches noir (4 ms) 21:26:59 L2ToL1Message siloing matches Noir (4 ms) 21:26:59 21:26:59 Test Suites: 1 passed, 1 total 21:26:59 Tests: 12 passed, 12 total 21:26:59 Snapshots: 12 passed, 12 total 21:26:59 Time: 1.711 s 21:26:59 Ran all test suites matching stdlib/src/hash/hash.test.ts. 21:26:59 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?