Parent Log:
http://ci.aztec-labs.com/11d263800318d38c
Command: 782f38c6306b3c5e yarn-project/scripts/run_test.sh simulator/src/public/avm/serialization/bytecode_serialization.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/d5a262aabc20f5384a720a0d831e2ec28badc7f9
Env: REF_NAME=gh-readonly-queue/next/pr-15042-17ea18ade041a1bb437806e047c30b29da124094 CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Wed Jun 18 18:09:09 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15042_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_c825b40a08525c8c_next
18:09:11
PASS src/public/avm/serialization/bytecode_serialization.test.ts
18:09:11 Bytecode Serialization
18:09:11
✓ Should deserialize using instruction set (3 ms)
18:09:11
✓ Should serialize using instruction.serialize() (2 ms)
18:09:11
✓ Should deserialize real instructions (2 ms)
18:09:11
✓ Should serialize real instructions (1 ms)
18:09:11
✓ Should throw an InvalidOpcodeError while deserializing an out-of-range opcode value (16 ms)
18:09:11
✓ Should throw an InvalidOpcodeError while deserializing an opcode value not in instruction set (1 ms)
18:09:11
✓ Should throw an AvmParsingError while deserializing an incomplete instruction (9 ms)
18:09:11
✓ Should throw an AvmParsingError while deserializing an incomplete instruction and a wrong tag value (1 ms)
18:09:11
✓ Should throw an InvalidTagValueError while deserializing a tag value out of range (11 ms)
18:09:11
18:09:11
Test Suites: 1 passed, 1 total
18:09:11
Tests: 9 passed, 9 total
18:09:11
Snapshots: 0 total
18:09:11
Time: 0.541 s
18:09:11
Ran all test suites matching simulator/src/public/avm/serialization/bytecode_serialization.test.ts
.
18:09:11
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?