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