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