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