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