Parent Log: http://ci.aztec-labs.com/ddad17d0c78b0b72 Command: f44e1b4f382283e1 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be1fa8aacb33d330cf496352bb1446439e34c51a Env: REF_NAME=gh-readonly-queue/next/pr-15162-7d1abcb337009939ee47da8445b5fee80f39fb58 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 10:04:42 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15162_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:04:46 PASS src/public/avm/avm_execution_environment.test.ts 10:04:46 Execution Environment 10:04:46 ✓ New call should fork execution environment correctly (6 ms) 10:04:46 ✓ New static call should fork execution environment correctly (1 ms) 10:04:46 10:04:46 Test Suites: 1 passed, 1 total 10:04:46 Tests: 2 passed, 2 total 10:04:46 Snapshots: 0 total 10:04:46 Time: 2.002 s 10:04:46 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 10:04:46 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?