Parent Log: http://ci.aztec-labs.com/5341f5baef09d91c Command: a73e94f3b52b3d94 yarn-project/scripts/run_test.sh simulator/src/public/avm/opcodes/control_flow.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/aa12cea18cfe4e45e23b46cf1a086d8331837eb5 Env: REF_NAME=db/simple-bc-hash CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 16 17:15:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=db_simple-bc-hash_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_90e5ee36fe3208b5_next 17:15:38 PASS src/public/avm/opcodes/control_flow.test.ts 17:15:38 Control Flow Opcodes 17:15:38 JUMP 17:15:38 ✓ Should (de)serialize correctly (9 ms) 17:15:38 ✓ Should implement JUMP (2 ms) 17:15:38 JUMPI 17:15:38 ✓ Should (de)serialize correctly (1 ms) 17:15:38 ✓ Should implement JUMPI - truthy (1 ms) 17:15:38 ✓ Should implement JUMPI - falsy (1 ms) 17:15:38 INTERNALCALL and INTERNALRETURN 17:15:38 ✓ INTERNALCALL Should (de)serialize correctly (1 ms) 17:15:38 ✓ Should implement Internal Call and Return (1 ms) 17:15:38 ✓ Should error if Internal Return is called without a corresponding Internal Call (10 ms) 17:15:38 17:15:38 Test Suites: 1 passed, 1 total 17:15:38 Tests: 8 passed, 8 total 17:15:38 Snapshots: 0 total 17:15:38 Time: 1.423 s 17:15:38 Ran all test suites matching simulator/src/public/avm/opcodes/control_flow.test.ts. 17:15:38 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?