Parent Log: http://ci.aztec-labs.com/a0a5ca8d8b3bb5c7 Command: f643ae060f517c84 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/hashing.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be78cf2e908c8f2f34676d72c74c8b92a3f591d1 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Fri Jun 20 23:00:16 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 23:00:18 PASS src/public/avm/opcodes/hashing.test.ts 23:00:18 Hashing Opcodes 23:00:18 Poseidon2 23:00:18 Should (de)serialize correctly (6 ms) 23:00:18 Should hash correctly - direct (213 ms) 23:00:18 Should hash correctly - indirect (2 ms) 23:00:18 Should throw an error when input state offsets are out of range. (20 ms) 23:00:18 Should throw an error when output state offsets are out of range. (1 ms) 23:00:18 Keccakf1600 23:00:18 Should (de)serialize correctly (1 ms) 23:00:18 Should permute correctly - direct (3 ms) 23:00:18 Should throw an error when message input offsets are out of range. (1 ms) 23:00:18 Should throw an error when destination offsets are out of range. (2 ms) 23:00:18 Sha256Compression 23:00:18 Should (de)serialize correctly (1 ms) 23:00:18 Should hash correctly - direct (2 ms) 23:00:18 Should hash correctly - indirect (1 ms) 23:00:18 Should throw an error when input offsets are out of range. (1 ms) 23:00:18 Should throw an error when state offsets are out of range. (1 ms) 23:00:18 Should throw an error when output offsets are out of range. (1 ms) 23:00:18 23:00:18 Test Suites: 1 passed, 1 total 23:00:18 Tests: 15 passed, 15 total 23:00:18 Snapshots: 0 total 23:00:18 Time: 1.585 s 23:00:18 Ran all test suites matching simulator/src/public/avm/opcodes/hashing.test.ts. 23:00:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?