Parent Log: http://ci.aztec-labs.com/fd27c7b524aab244 Command: f803628267cda2b6 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/21a568ac0c9ef351b1923375be41d4620add2b60 Env: REF_NAME=gh-readonly-queue/next/pr-15042-b80949775e5c27908a6055ad24592f7d98bdc45a CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Sun Jun 15 12:35:12 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 12:35:14 PASS src/public/avm/avm_execution_environment.test.ts 12:35:14 Execution Environment 12:35:14 ✓ New call should fork execution environment correctly (7 ms) 12:35:14 ✓ New static call should fork execution environment correctly (1 ms) 12:35:14 12:35:14 Test Suites: 1 passed, 1 total 12:35:14 Tests: 2 passed, 2 total 12:35:14 Snapshots: 0 total 12:35:14 Time: 1.978 s 12:35:14 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 12:35:14 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?