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