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