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