Parent Log:
http://ci.aztec-labs.com/6dc709803944a101
Command: 5c58d0b0e69f02f7 yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/7339c264ad706420ee9babb0dd1b6ed793e97402
Env: REF_NAME=gh-readonly-queue/next/pr-15039-ddabb45f79cc171e41a0a5330544775de9fdf7fd CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Fri Jun 13 15:03:16 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15039_amd64_x2-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next
15:03:18
PASS src/public/avm/serialization/bytecode_serialization.test.ts
15:03:18 Bytecode Serialization
15:03:18
✓ Should deserialize using instruction set (8 ms)
15:03:18
✓ Should serialize using instruction.serialize() (4 ms)
15:03:18
✓ Should deserialize real instructions (5 ms)
15:03:18
✓ Should serialize real instructions (1 ms)
15:03:18
✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (19 ms)
15:03:18
✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (2 ms)
15:03:18
✓ Should throw an AvmParsingError while deserializing an incomplete instruction (14 ms)
15:03:18
✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms)
15:03:18
✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (14 ms)
15:03:18
15:03:18
Test Suites: 1 passed, 1 total
15:03:18
Tests: 9 passed, 9 total
15:03:18
Snapshots: 0 total
15:03:18
Time: 0.798 s
15:03:18
Ran all test suites matching /simulator\/src\/public\/avm\/serialization\/bytecode_serialization.test.ts/i
.
15:03:18
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?