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