Grinder contains output - unexpected argument '2048'

**Describe the bug**
Running an internal grinder I noticed the following weird output, which didn't cause any failure.
```
13:04:35 expr: non-integer argument
13:04:35 expr: syntax error: unexpected argument '2048'
13:04:35 expr: syntax error: missing argument after '>'
```

With more context
```
13:04:29 Running jdk_custom_0 ...
13:04:29 There are 1 test targets in jdk_custom_0
13:04:29 "C:/Users/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image\\bin\\java" -version
13:04:31 openjdk version "11.0.18" 2023-01-17
13:04:31 IBM Semeru Runtime Open Edition 11.0.18.0 (build 11.0.18+10)
13:04:31 Eclipse OpenJ9 VM 11.0.18.0 (build openj9-0.36.0, JRE 11 Windows Server 2019 amd64-64-Bit Compressed References 20230207_562 (JIT enabled, AOT enabled)
13:04:31 OpenJ9 - e68fb241f
13:04:31 OMR - f491bbf6f
13:04:31 JCL - b732de1eee based on jdk-11.0.18+10)
13:04:32 make[2]: Entering directory '/cygdrive/c/Users/jenkins/workspace/Grinder/aqa-tests'
13:04:32 make[3]: Entering directory '/cygdrive/c/Users/jenkins/workspace/Grinder/aqa-tests/openjdk'
13:04:35 expr: non-integer argument
13:04:35 expr: syntax error: unexpected argument '2048'
13:04:35 expr: syntax error: missing argument after '>'
13:04:36
13:04:37 ===============================================
13:04:37 Running test jdk_custom_0 ...
13:04:37 ===============================================
```

**To Reproduce**
I'm running on Windows building openjdk running jdk_custom_0 with java/security/SecureRandom/ApiTest.java on a custom build of jdk11 (I don't expect the build matters). TKG_ITERATIONS is 3 and EXIT_FAILURE true. A machine label is set.

https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/parambuild/?TARGET=jdk_custom_0&SDK_RESOURCE=customized&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=15&EXTRA_DOCKER_ARGS=-v+%24%7BTEST_JDK_HOME%7D%3A%2Fopt%2Fjava%2Fopenjdk&VENDOR_TEST_DIRS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=false&KEEP_REPORTDIR=false&PERSONAL_BUILD=true&DOCKER_REGISTRY_DIR=&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&RERUN_ITERATIONS=0&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=win19x86-rt2-1.fyre.ibm.com&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=https%3A%2F%2Fna.artifactory.swg-devops.com%2Fartifactory%2Fsys-rt-generic-local%2Fhyc-runtimes-jenkins.swg-devops.com%2Fbuild-scripts%2Fjobs%2Fjdk11u%2Fjdk11u-windows-x64-openj9%2F562%2Fibm-semeru-open-jdk_x64_windows_11.0.18_10_openj9-0.36.1.zip&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&ARTIFACTORY_SERVER=na.artifactory.swg-devops&KEEP_WORKSPACE=false&CURL_OPTS=&JDK_VERSION=11&USER_CREDENTIALS_ID=&DOCKER_REGISTRY_URL=&ITERATIONS=1&EXIT_FAILURE=true&EXIT_SUCCESS=false&VENDOR_TEST_REPOS=&JCK_GIT_BRANCH=main&JDK_REPO=&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=git%40github.ibm.com%3Aruntimes%2FJCKnext-unzipped.git&RELEASE_TAG=&VENDOR_TEST_BRANCHES=&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&UPSTREAM_JOB_NAME=&CLOUD_PROVIDER=&CUSTOM_TARGET=java%2Fsecurity%2FSecureRandom%2FApiTest.java&DEBUG_IMAGES_REQUIRED=false&CODE_COVERAGE=false&VENDOR_TEST_SHAS=&JDK_BRANCH=&TEST_IMAGES_REQUIRED=true&LABEL_ADDITION=ci.project.openj9&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=nightly&JDK_IMPL=openj9&TEST_TIME=&SSH_AGENT_CREDENTIAL=83181e25-eea4-4f55-8b3e-e79615733226&AUTO_DETECT=true&SLACK_CHANNEL=%23rt-jenkins&DYNAMIC_COMPILE=true&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&TKG_ITERATIONS=3&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=4e18ffe7-b1b1-4272-9979-99769b68bcc2&ARCHIVE_TEST_RESULTS=false&NUM_MACHINES=1&TRSS_URL=http%3A%2F%2Ftrss1.fyre.ibm.com&BUILD_LIST=openjdk&USE_TESTENV_PROPERTIES=false&UPSTREAM_JOB_NUMBER=&STF_OWNER_BRANCH=adoptium%3Amaster&BUILDS_TO_KEEP=100&TIME_LIMIT=10&JVM_OPTIONS=&PARALLEL=NodesByIterations

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.

Start by reproducing the Windows run for target jdk_custom_0 with java/security/SecureRandom/ApiTest.java and TKG_ITERATIONS=3. Trace the Grinder or openjdk test-infrastructure entry point that emits the expr messages under Cygwin, then verify the test completes without those unexpected errors.

Written by the indexing model from the issue text.