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