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