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