Some tests in test/hotspot/jtreg/vmTestbase/nsk tests are misusing the -iterations command-line option: it is parsed only as "-iterations x" rather than "-iterations=x"
Fixing the RunParams parsing to recognise this saves updating multiple tests. Other options are "option=value" so accepting -iterations=number is what we might expect (and is what tests are currently written to use). The change makes logs look correct. No more "Iterations: 0". There are tests that currently log "Iterations: 0" but still do some work, so this is partly cosmetic, but also if you were thinking of making a test do some set limited number of iterations, you can now follow the example of other tests and have it work. ------------- Commit messages: - 8373917: test/hotspot/jtreg/vmTestbase/nsk/monitoring: -iterations setting misused in tests Changes: https://git.openjdk.org/jdk/pull/28876/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=28876&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8373917 Stats: 7 lines in 1 file changed: 5 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/28876.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28876/head:pull/28876 PR: https://git.openjdk.org/jdk/pull/28876
