Parent Log: http://ci.aztec-labs.com/d05c8a11bc1fb346 Command: 715772c6bcfd0ed3 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3863bc02d671057d0cffd4ced17ca317788ff190 Env: REF_NAME=gh-readonly-queue/staging/pr-15238-db396f13b7ef374a230174bdc4078d9fbb3c788a CURRENT_VERSION=1.0.0 CI_FULL=0 Date: Tue Jun 24 12:18:56 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15238_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_staging 12:18:59 PASS src/public/avm/avm_execution_environment.test.ts 12:18:59 Execution Environment 12:18:59 ✓ New call should fork execution environment correctly (5 ms) 12:18:59 ✓ New static call should fork execution environment correctly (1 ms) 12:18:59 12:18:59 Test Suites: 1 passed, 1 total 12:18:59 Tests: 2 passed, 2 total 12:18:59 Snapshots: 0 total 12:18:59 Time: 1.263 s 12:18:59 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 12:18:59 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?