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