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