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