don't time out caliper runs

[GoogleCodeExporter]

~/local-disk/dd1$ vogar 
~/Projects/dalvik/benchmarks/regression/CharsetBenchmark.java 
Actions: 1
Action benchmarks.regression.CharsetBenchmark
     0% Scenario{vm=dalvikvm, benchmark=_getBytes_ISO_8859_1} 94666.83ns; 
U+03C3=911.39ns @ 7 trials
    17% Scenario{vm=dalvikvm, benchmark=_getBytes_ISO_8859_1_non_canonical} 
98487.44ns; U+03C3=964.74ns @ 7 trials
    33% Scenario{vm=dalvikvm, benchmark=_getBytes_US_ASCII} 94439.73ns; 
U+03C3=1191.85ns @ 10 trials
    50% Scenario{vm=dalvikvm, benchmark=_getBytes_US_ASCII_non_canonical} 
98379.25ns; U+03C3=2571.53ns @ 10 trials
    67% Scenario{vm=dalvikvm, benchmark=_getBytes_UTF_8} 89514.93ns; 
U+03C3=418.28ns @ 3 trials
    83% Scenario{vm=dalvikvm, benchmark=_getBytes_UTF_8_non_canonical}
    killed because it timed out after 60 seconds
  FAIL (EXEC_TIMEOUT)
executing adb shell rm -r /sdcard/vogarFailure summary:
benchmarks.regression.CharsetBenchmark
Skip summary:
Outcomes: 1. Passed: 0, Failed: 1, Skipped: 0. Took 1m5s.
~/local-disk/dd1$ 

it's a benchmark. i don't know how long it will take. it can easily take a 
long time (several minutes) to go through all the variants. caliper should 
default to a really long time out.

(running arbitrary java via a "main" method should default to _no_ timeout, 
if it doesn't already.)

Original issue reported on code.google.com by e...@google.com on 7 Jun 2010 at 5:48

[GoogleCodeExporter]

Original comment by e...@google.com on 7 Jun 2010 at 5:48

• Changed title: don't time out caliper runs

[GoogleCodeExporter]

gah! this keeps biting me:

  FAIL (EXEC_TIMEOUT)
Failure summary:
benchmarks.regression.NativeMethodBenchmark
Outcomes: 1. Passed: 0, Failed: 1, Skipped: 0. Took 1m6s.

Original comment by e...@google.com on 16 Jun 2010 at 7:07

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

ben fixed this.

Original comment by e...@google.com on 22 Jun 2010 at 10:10

• Changed state: Fixed