Parent Log:
http://ci.aztec-labs.com/64e2bdc106a2b1fc
Command: e5b0f4b393972465 yarn-project/scripts/run_test.sh foundation/src/crypto/sha256/index.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/a8c553f203c98e5ca274e763c8e51daaaaf760d6
Env: REF_NAME=gh-readonly-queue/next/pr-15017-30660269b33bab8cca354c41659533acf4d48e07 CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Fri Jun 13 09:41:59 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15017_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_379c156cca6452a9_next
09:42:00
PASS src/crypto/sha256/index.test.ts
09:42:00 sha256
09:42:00 sha256 hash
09:42:00
✓ should correctly hash data using hash.js (5 ms)
09:42:00 sha256 compression
09:42:00
✓ sha256Compression works (1 ms)
09:42:00
✓ sha256 compression does not work on state.length < 8 (10 ms)
09:42:00
✓ sha256 compression does not work on state.length > 8 (3 ms)
09:42:00
✓ sha256 compression does not work on inputs.length < 16 (1 ms)
09:42:00
✓ sha256 compression does not work on inputs.length > 16 (1 ms)
09:42:00
09:42:00
Test Suites: 1 passed, 1 total
09:42:00
Tests: 6 passed, 6 total
09:42:00
Snapshots: 0 total
09:42:00
Time: 0.423 s
09:42:00
Ran all test suites matching /foundation\/src\/crypto\/sha256\/index.test.ts/i
.
09:42:00
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?