Parent Log: http://ci.aztec-labs.com/4c9c6ce753b843f4 Command: 6d103549f0f4c9d2 yarn-project/scripts/run_test.sh foundation/src/crypto/sha256/index.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/534f06e45f48274efd53a2204c90cb0b91a53efb Env: REF_NAME=gh-readonly-queue/next/pr-15230-ad85cda24c2f9b5b4b17d4921f8597b71949bb6c CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 20:49:08 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15230_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_379c156cca6452a9_next 20:49:10 PASS src/crypto/sha256/index.test.ts 20:49:10 sha256 20:49:10 sha256 hash 20:49:10 ✓ should correctly hash data using hash.js (7 ms) 20:49:10 sha256 compression 20:49:10 ✓ sha256Compression works (2 ms) 20:49:10 ✓ sha256 compression does not work on state.length < 8 (21 ms) 20:49:10 ✓ sha256 compression does not work on state.length > 8 (2 ms) 20:49:10 ✓ sha256 compression does not work on inputs.length < 16 (2 ms) 20:49:10 ✓ sha256 compression does not work on inputs.length > 16 (1 ms) 20:49:10 20:49:10 Test Suites: 1 passed, 1 total 20:49:10 Tests: 6 passed, 6 total 20:49:10 Snapshots: 0 total 20:49:10 Time: 0.829 s 20:49:10 Ran all test suites matching foundation/src/crypto/sha256/index.test.ts. 20:49:10 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?