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