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