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