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