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