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