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