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