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