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