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