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