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