Parent Log: http://ci.aztec-labs.com/b6da8d4f9c176ddf Command: 0e6cfc077fbe1818 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/control_flow.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f17855f94a58189a98dd378743e67b774ea38144 Env: REF_NAME=gh-readonly-queue/next/pr-15066-47bd93499e6606131b6ececa3536632cf5e84409 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 10:00:57 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15066_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_90e5ee36fe3208b5_next 10:00:59 PASS src/public/avm/opcodes/control_flow.test.ts 10:00:59 Control Flow Opcodes 10:00:59 JUMP 10:00:59 Should (de)serialize correctly (7 ms) 10:00:59 Should implement JUMP (2 ms) 10:00:59 JUMPI 10:00:59 Should (de)serialize correctly (1 ms) 10:00:59 Should implement JUMPI - truthy (1 ms) 10:00:59 Should implement JUMPI - falsy (1 ms) 10:00:59 INTERNALCALL and INTERNALRETURN 10:00:59 INTERNALCALL Should (de)serialize correctly (1 ms) 10:00:59 Should implement Internal Call and Return (1 ms) 10:00:59 Should error if Internal Return is called without a corresponding Internal Call (12 ms) 10:00:59 10:00:59 Test Suites: 1 passed, 1 total 10:00:59 Tests: 8 passed, 8 total 10:00:59 Snapshots: 0 total 10:00:59 Time: 1.492 s 10:00:59 Ran all test suites matching simulator/src/public/avm/opcodes/control_flow.test.ts. 10:00:59 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?