From 8cb88103a8c4ea4f5cff574fc10735210c8236df Mon Sep 17 00:00:00 2001 From: Richard Uhler Date: Tue, 7 Mar 2017 13:53:32 +0000 Subject: [PATCH] Experiment with ulimit settings to see if it fixes test failure. RELOCATE test is failing on a build bot with file size limit exceeded. The suspicion is ANDROID_HOST_OUT is being set oddly on the build bot so we don't find the right directory to use as the basis for setting the ulimit on RELOCATE and end up with much too small a limit. Test: test-art-host Change-Id: I18bc6cf1888a4831a313aaaba6fab4f689825284 --- test/etc/run-test-jar | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/test/etc/run-test-jar b/test/etc/run-test-jar index 0ac5481f6..3f2e3c82f 100755 --- a/test/etc/run-test-jar +++ b/test/etc/run-test-jar @@ -455,11 +455,12 @@ if [ "$RELOCATE" = "y" ]; then else FLAGS="$FLAGS -Xnorelocate" COMPILE_FLAGS="${COMPILE_FLAGS} --runtime-arg -Xnorelocate" - if [ "$HOST" = "y" ]; then - # Increase ulimit to 128MB in case we are running hprof test, - # or string append test with art-debug-gc. - ulimit -S 128000 || exit 1 - fi +fi + +if [ "$HOST" = "y" ]; then + # Increase ulimit to 128MB in case we are running hprof test, + # or string append test with art-debug-gc. + ulimit -S 128000 || exit 1 fi if [ "$HOST" = "n" ]; then -- 2.11.0