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