Parent Log: http://ci.aztec-labs.com/090e33d2919b194d Command: 3aa3a54f792fc08a yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/2868628b6ae039db35b4267ab3975abc64a5d9b4 Env: REF_NAME=gh-readonly-queue/next/pr-15179-227fd751f8d3e07a96e4c1564665f0676f8222af CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 23 12:42:03 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15179_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 12:42:06 PASS src/public/avm/avm_execution_environment.test.ts 12:42:06 Execution Environment 12:42:06 ✓ New call should fork execution environment correctly (8 ms) 12:42:06 ✓ New static call should fork execution environment correctly (2 ms) 12:42:06 12:42:06 Test Suites: 1 passed, 1 total 12:42:06 Tests: 2 passed, 2 total 12:42:06 Snapshots: 0 total 12:42:06 Time: 1.869 s 12:42:06 Ran all test suites matching simulator/src/public/avm/avm_execution_environment.test.ts. 12:42:06 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?