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