Parent Log: http://ci.aztec-labs.com/5341f5baef09d91c Command: a73e94f3b52b3d94 yarn-project/scripts/run_test.sh stdlib/src/hash/hash.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/aa12cea18cfe4e45e23b46cf1a086d8331837eb5 Env: REF_NAME=db/simple-bc-hash CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 16 17:15:44 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=db_simple-bc-hash_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ea5bb2ff7a555cb0_next 17:15:47 PASS src/hash/hash.test.ts 17:15:47 hash 17:15:47 ✓ computes note hash nonce (253 ms) 17:15:47 ✓ computes unique note hash (2 ms) 17:15:47 ✓ computes siloed note hash (2 ms) 17:15:47 ✓ computes siloed nullifier (1 ms) 17:15:47 ✓ computes public data tree value (1 ms) 17:15:47 ✓ computes public data tree leaf slot (1 ms) 17:15:47 ✓ hashes empty function args 17:15:47 ✓ hashes function args (1 ms) 17:15:47 ✓ hashes many function args (7 ms) 17:15:47 ✓ compute secret message hash (1 ms) 17:15:47 ✓ Var args hash matches noir (2 ms) 17:15:47 ✓ L2ToL1Message siloing matches Noir (4 ms) 17:15:47 17:15:47 Test Suites: 1 passed, 1 total 17:15:47 Tests: 12 passed, 12 total 17:15:47 Snapshots: 12 passed, 12 total 17:15:47 Time: 1.799 s 17:15:47 Ran all test suites matching stdlib/src/hash/hash.test.ts. 17:15:47 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?