Parent Log: http://ci.aztec-labs.com/b325d16c0a95c660 Command: 4f771e618b80a60c yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_memory_types.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/991b313d676f7cf820bb62a33e57cf5a4c8cf9cf Env: REF_NAME=gh-readonly-queue/next/pr-15075-af42fafbeb7d6a4440329d9e9e5b1df459fa2e2e CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:02:23 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15075_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_aaee828035f5cfae_next 16:02:25 PASS src/public/avm/avm_memory_types.test.ts 16:02:25 TaggedMemory 16:02:25 Elements should be Field(0) after construction (4 ms) 16:02:25 Should set and get integral types (1 ms) 16:02:25 Should set and get field elements 16:02:25 Slice should get Field(0) on unset elements (1 ms) 16:02:25 Should set and get slices 16:02:25 Should access and write in last index of memory 16:02:25 Should not access beyond memory last index (36 ms) 16:02:25 Integral Types (U1 only) 16:02:25 Uint1 16:02:25 Should construct a new Uint1 from a number 16:02:25 Should construct a new Uint1 from a bigint 16:02:25 Should build a new Uint1 16:02:25 Should add two Uint1 correctly (1 ms) 16:02:25 Should subtract two Uint1 correctly 16:02:25 Should multiply two Uint1 correctly (1 ms) 16:02:25 Should divide two Uint1 correctly 16:02:25 Should shift right Uint1 correctly (1 ms) 16:02:25 Should shift left Uint1 correctly 16:02:25 Should and two Uint1 correctly (1 ms) 16:02:25 Should or two Uint1 correctly 16:02:25 Should xor two Uint1 correctly 16:02:25 Should check equality of two Uint1 correctly (1 ms) 16:02:25 Should check if one Uint1 is less than another correctly 16:02:25 Integral Types (excluding U1) 16:02:25 Uint8 16:02:25 Should construct a new Uint8 from a number 16:02:25 Should construct a new Uint8 from a bigint 16:02:25 Should build a new Uint8 16:02:25 Should add two Uint8 correctly 16:02:25 Should subtract two Uint8 correctly (1 ms) 16:02:25 Should multiply two Uint8 correctly 16:02:25 Should divide two Uint8 correctly 16:02:25 Should shift right Uint8 correctly 16:02:25 Should shift left Uint8 correctly 16:02:25 Should and two Uint8 correctly (1 ms) 16:02:25 Should or two Uint8 correctly 16:02:25 Should xor two Uint8 correctly 16:02:25 Should check equality of two Uint8 correctly (1 ms) 16:02:25 Should check if one Uint8 is less than another correctly 16:02:25 Uint16 16:02:25 Should construct a new Uint16 from a number 16:02:25 Should construct a new Uint16 from a bigint (1 ms) 16:02:25 Should build a new Uint16 16:02:25 Should add two Uint16 correctly 16:02:25 Should subtract two Uint16 correctly (1 ms) 16:02:25 Should multiply two Uint16 correctly 16:02:25 Should divide two Uint16 correctly 16:02:25 Should shift right Uint16 correctly (1 ms) 16:02:25 Should shift left Uint16 correctly 16:02:25 Should and two Uint16 correctly 16:02:25 Should or two Uint16 correctly (1 ms) 16:02:25 Should xor two Uint16 correctly 16:02:25 Should check equality of two Uint16 correctly 16:02:25 Should check if one Uint16 is less than another correctly (1 ms) 16:02:25 Uint32 16:02:25 Should construct a new Uint32 from a number 16:02:25 Should construct a new Uint32 from a bigint (1 ms) 16:02:25 Should build a new Uint32 16:02:25 Should add two Uint32 correctly 16:02:25 Should subtract two Uint32 correctly (1 ms) 16:02:25 Should multiply two Uint32 correctly 16:02:25 Should divide two Uint32 correctly 16:02:25 Should shift right Uint32 correctly (1 ms) 16:02:25 Should shift left Uint32 correctly 16:02:25 Should and two Uint32 correctly 16:02:25 Should or two Uint32 correctly (1 ms) 16:02:25 Should xor two Uint32 correctly 16:02:25 Should check equality of two Uint32 correctly 16:02:25 Should check if one Uint32 is less than another correctly (1 ms) 16:02:25 Uint64 16:02:25 Should construct a new Uint64 from a number 16:02:25 Should construct a new Uint64 from a bigint 16:02:25 Should build a new Uint64 (1 ms) 16:02:25 Should add two Uint64 correctly 16:02:25 Should subtract two Uint64 correctly 16:02:25 Should multiply two Uint64 correctly 16:02:25 Should divide two Uint64 correctly 16:02:25 Should shift right Uint64 correctly 16:02:25 Should shift left Uint64 correctly 16:02:25 Should and two Uint64 correctly (1 ms) 16:02:25 Should or two Uint64 correctly 16:02:25 Should xor two Uint64 correctly 16:02:25 Should check equality of two Uint64 correctly (1 ms) 16:02:25 Should check if one Uint64 is less than another correctly 16:02:25 Uint128 16:02:25 Should construct a new Uint128 from a number (1 ms) 16:02:25 Should construct a new Uint128 from a bigint 16:02:25 Should build a new Uint128 16:02:25 Should add two Uint128 correctly (1 ms) 16:02:25 Should subtract two Uint128 correctly 16:02:25 Should multiply two Uint128 correctly 16:02:25 Should divide two Uint128 correctly (1 ms) 16:02:25 Should shift right Uint128 correctly 16:02:25 Should shift left Uint128 correctly 16:02:25 Should and two Uint128 correctly (1 ms) 16:02:25 Should or two Uint128 correctly 16:02:25 Should xor two Uint128 correctly 16:02:25 Should check equality of two Uint128 correctly 16:02:25 Should check if one Uint128 is less than another correctly 16:02:25 Field 16:02:25 Should build a new Field 16:02:25 Should add two Fields correctly (1 ms) 16:02:25 Should subtract two Fields correctly 16:02:25 Should multiply two Fields correctly (1 ms) 16:02:25 Should divide two Fields correctly 16:02:25 Should check equality of two Fields correctly (1 ms) 16:02:25 Should check if one Field is less than another correctly 16:02:25 Should convert Field to BigInt correctly 16:02:25 16:02:25 Test Suites: 1 passed, 1 total 16:02:25 Tests: 99 passed, 99 total 16:02:25 Snapshots: 0 total 16:02:25 Time: 0.834 s 16:02:25 Ran all test suites matching simulator/src/public/avm/avm_memory_types.test.ts. 16:02:25 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?