Tests hit I see java.lang.NoSuchMethodError: exception

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Ran a bunch of tests comparing two methods
2. The individual tests ran k. 
3. When it starts the longer experiments it times out around 5 mins. I am not 
sure why the code take too long.

What is the expected output? What do you see instead?
Finishing of the tests with the result of the experiments uploaded to the web.
I see java.lang.NoSuchMethodError: 
org.apache.commons.math.stat.descriptive.rank.Percentile.setData([D)V
    at com.google.caliper.runner.ConsoleResultProcessor.processTrial(ConsoleResultProcessor.java:86)
    at com.google.caliper.runner.ExperimentingCaliperRun.run(ExperimentingCaliperRun.java:231)
    at com.google.caliper.runner.CaliperMain.exitlessMain(CaliperMain.java:135)
    at com.google.caliper.runner.CaliperMain.main(CaliperMain.java:78)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
    at java.lang.Thread.run(Thread.java:724)

Also when it started the experiment it gave : Starting experiment 1 of 4: 
{instrument=allocation, benchmarkMethod=fetchCacheLessOptimal, vm=default, 
parameters={concurrency=200}}… ERROR: Trial failed to complete (its results 
will not be included in the run):
  Trial exceeded the total allowable runtime (5m). The limit may be adjusted using the --time-limit flag.

What version of the product are you using? On what operating system?
OS- MacOS X 10.8.5
version- 1.0-beta-SNAPSHOT

Attaching files to get an idea of what I am doing.

Original issue reported on code.google.com by forman...@gmail.com on 26 Nov 2013 at 9:47

Attachments:

• CacheBenchmark.java
• CachePerformanceTest.java
• Cache.java

[GoogleCodeExporter]

I don't know of any reason why Caliper would get a NSME.  I wonder if there's a 
dependency conflict or something going on there.  Does mvn dependency:analyze 
report anything suspicious?

Original comment by gak@google.com on 27 Nov 2013 at 3:22

[GoogleCodeExporter]

Oh, and as for the second part…  It looks like you're running a pretty 
heavyweight benchmark.  By default Caliper is set up to run microbenchmarks 
(https://code.google.com/p/caliper/wiki/JavaMicrobenchmarks), so any run that 
takes longer than 5 min. would be highly suspicious and likely broken.  The 
solution is right in the output: "The limit may be adjusted using the 
--time-limit flag"

Original comment by gak@google.com on 27 Nov 2013 at 3:27

[GoogleCodeExporter]

I think this issue can be closed. After I upgraded the version of math 
libraries on my pom file, this went away.

Original comment by forman...@gmail.com on 6 Dec 2013 at 6:43

[GoogleCodeExporter]

The other problem I  am seeing even when I allocate about 4 gigs of memory 
during runtime instrumentation, I see warnings of high GC! Is it possible that 
I have to allocate more ?

Original comment by forman...@gmail.com on 6 Dec 2013 at 6:45

[GoogleCodeExporter]

Glad you fixed the issue.  It might be possible that you need more heap.  For 
instance, a loop that adds two ints, but boxes the result will end up with a 
small amount per rep, but a lot of reps.

Original comment by gak@google.com on 6 Dec 2013 at 6:53

• Changed state: Obsolete