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