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