Parent Log: http://ci.aztec-labs.com/1c420a977384450c Command: 426cee6a32f1da3c yarn-project/scripts/run_test.sh foundation/src/crypto/sha256/index.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/d96baf1c44329e8b2e3a432ad803f702f5184a62 Env: REF_NAME=gh-readonly-queue/next/pr-15025-26c5a39fe03723d11540f721293d7aebd1f478d9 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 09:32:49 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15025_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_379c156cca6452a9_next 09:32:50 PASS src/crypto/sha256/index.test.ts 09:32:50 sha256 09:32:50 sha256 hash 09:32:50 ✓ should correctly hash data using hash.js (25 ms) 09:32:50 sha256 compression 09:32:50 ✓ sha256Compression works (2 ms) 09:32:50 ✓ sha256 compression does not work on state.length < 8 (17 ms) 09:32:50 ✓ sha256 compression does not work on state.length > 8 (2 ms) 09:32:50 ✓ sha256 compression does not work on inputs.length < 16 (17 ms) 09:32:50 ✓ sha256 compression does not work on inputs.length > 16 (1 ms) 09:32:50 09:32:50 Test Suites: 1 passed, 1 total 09:32:50 Tests: 6 passed, 6 total 09:32:50 Snapshots: 0 total 09:32:50 Time: 0.574 s 09:32:50 Ran all test suites matching /foundation\/src\/crypto\/sha256\/index.test.ts/i. 09:32:50 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?