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