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