Parent Log: http://ci.aztec-labs.com/e288acb99b2d3432 Command: d22bc4a94b0d21bc yarn-project/scripts/run_test.sh simulator/src/public/avm/avm_execution_environment.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/c06f30929f18b85bcea93c0926a8d640a3819f00 Env: REF_NAME=gh-readonly-queue/master/pr-15074-2707ec99de02004f3e30e7af0810e0d741ab9794 CURRENT_VERSION=0.87.8 CI_FULL=0 Date: Mon Jun 16 16:26:34 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15074_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_8341de5fa643616c_master 16:26:36 PASS src/public/avm/avm_execution_environment.test.ts 16:26:36 Execution Environment 16:26:36 ✓ New call should fork execution environment correctly (5 ms) 16:26:36 ✓ New static call should fork execution environment correctly (1 ms) 16:26:36 16:26:36 Test Suites: 1 passed, 1 total 16:26:36 Tests: 2 passed, 2 total 16:26:36 Snapshots: 0 total 16:26:36 Time: 1.16 s 16:26:36 Ran all test suites matching /simulator\/src\/public\/avm\/avm_execution_environment.test.ts/i. 16:26:36 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?