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