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