Parent Log: http://ci.aztec-labs.com/a079291c5cb4bf29 Command: 9e580e2a65a38075 yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/184d5f7d956dd7251670a2dd6728f313cfdf3caf Env: REF_NAME=gh-readonly-queue/next/pr-14822-e56baa7f24bac54baf9e2f22f6f33ae6fa8b8c0f CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Fri Jun 13 21:21:46 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14822_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_next 21:21:48 PASS src/public/avm/avm_execution_environment.test.ts 21:21:48 Execution Environment 21:21:48 ✓ New call should fork execution environment correctly (4 ms) 21:21:48 ✓ New static call should fork execution environment correctly (1 ms) 21:21:48 21:21:48 Test Suites: 1 passed, 1 total 21:21:48 Tests: 2 passed, 2 total 21:21:48 Snapshots: 0 total 21:21:48 Time: 1.306 s 21:21:48 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 21:21:48 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?