Parent Log: http://ci.aztec-labs.com/a0947d4e5c3fb9d9 Command: 3cad4e1fd0756a5c yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/e9a2301883801edbe36ea8bba05dcca7e714f30a Env: REF_NAME=gh-readonly-queue/master/pr-15131-464e1a9d9b40b5188586643b44bc52bffccbc3e6 CURRENT_VERSION=0.87.8 CI_FULL=1 Date: Wed Jun 18 12:52:06 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15131_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_master 12:52:08 PASS src/public/avm/avm_execution_environment.test.ts 12:52:08 Execution Environment 12:52:08 ✓ New call should fork execution environment correctly (7 ms) 12:52:08 ✓ New static call should fork execution environment correctly (1 ms) 12:52:08 12:52:08 Test Suites: 1 passed, 1 total 12:52:08 Tests: 2 passed, 2 total 12:52:08 Snapshots: 0 total 12:52:08 Time: 1.585 s 12:52:08 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 12:52:08 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?