Parent Log: http://ci.aztec-labs.com/a25636d452723f66 Command: d634b34c6dd762bb yarn-project/scripts/run_test.sh cli/src/utils/commands.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9b801754ba98479ee645488c29d2fda1eecbfd85 Env: REF_NAME=gh-readonly-queue/next/pr-14963-ee3655e025191bc85c5b3d3122eeedb44e38ffb2 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 20:57:00 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14963_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_4667fce1f8117690_next 20:57:03 PASS src/utils/commands.test.ts 20:57:03 parseFieldFromHexString 20:57:03 parses the field 0 correctly (4 ms) 20:57:03 parses the field 0x0 correctly (1 ms) 20:57:03 parses the field 0x1 correctly 20:57:03 parses the field 0x00 correctly (1 ms) 20:57:03 parses the field fa correctly (1 ms) 20:57:03 parses the field 123 correctly 20:57:03 parses the field 0xff correctly 20:57:03 parses the field 0x0000000000000000000000000000000000000000000000000000000000000003 correctly (1 ms) 20:57:03 parses the field 0x00000000000000000000000000000000000000000000000000000000000000003 correctly (1 ms) 20:57:03 20:57:03 Test Suites: 1 passed, 1 total 20:57:03 Tests: 9 passed, 9 total 20:57:03 Snapshots: 0 total 20:57:03 Time: 1.4 s 20:57:03 Ran all test suites matching cli/src/utils/commands.test.ts. 20:57:03 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?