Please review the following patch, which fixes the mentioned test case for memory constrained devices. This can be tested on a linux based development machine, using systemd as follows:
$ systemd-run --user --scope -p MemoryMax=800M -p MemorySwapMax=0 /usr/bin/make TEST="test/jdk/java/lang/String/StringRepeat.java" run-test I split up the test case in a part which only executes the small repeat counts, and in one part which executes the huge repeat count. The second part is guarded by a requirement, so it is only executed if enough memory is available. ------------- Commit messages: - Adds a second test instance which executes the huge repeat count. Changes: https://git.openjdk.java.net/jdk/pull/3566/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=3566&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8265421 Stats: 18 lines in 1 file changed: 13 ins; 1 del; 4 mod Patch: https://git.openjdk.java.net/jdk/pull/3566.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/3566/head:pull/3566 PR: https://git.openjdk.java.net/jdk/pull/3566
