Parent Log: http://ci.aztec-labs.com/820a0bb63168d9da Command: b895a7fa8f839b60 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/hashing.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/408ec6f57f38faf5e1dbdf7712a82e2e1112be2c Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Sat Jun 14 11:24:37 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_124e86f395aa5cc5_next 11:24:39 PASS src/public/avm/opcodes/hashing.test.ts 11:24:39 Hashing Opcodes 11:24:39 Poseidon2 11:24:39 Should (de)serialize correctly (7 ms) 11:24:39 Should hash correctly - direct (212 ms) 11:24:39 Should hash correctly - indirect (3 ms) 11:24:39 Should throw an error when input state offsets are out of range. (24 ms) 11:24:39 Should throw an error when output state offsets are out of range. (2 ms) 11:24:39 Keccakf1600 11:24:39 Should (de)serialize correctly (2 ms) 11:24:39 Should permute correctly - direct (4 ms) 11:24:39 Should throw an error when message input offsets are out of range. (2 ms) 11:24:39 Should throw an error when destination offsets are out of range. (2 ms) 11:24:39 Sha256Compression 11:24:39 Should (de)serialize correctly (1 ms) 11:24:39 Should hash correctly - direct (3 ms) 11:24:39 Should hash correctly - indirect (1 ms) 11:24:39 Should throw an error when input offsets are out of range. (1 ms) 11:24:39 Should throw an error when state offsets are out of range. (1 ms) 11:24:39 Should throw an error when output offsets are out of range. (1 ms) 11:24:39 11:24:39 Test Suites: 1 passed, 1 total 11:24:39 Tests: 15 passed, 15 total 11:24:39 Snapshots: 0 total 11:24:39 Time: 1.544 s 11:24:39 Ran all test suites matching /simulator\/src\/public\/avm\/opcodes\/hashing.test.ts/i. 11:24:39 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?