Caliper fails ObjectGraphMeasurerTest

[GoogleCodeExporter]

What steps will reproduce the problem?
1. cd into caliper
2. run: mvn eclipse:configure-workspace eclipse:eclipse install

What is the expected output? What do you see instead?
I expect to see notification for maven indicating that the project successfully 
built and passed tests,

I see:

Running com.google.caliper.memory.ObjectGraphMeasurerTest
Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec <<< 
FAILURE!

Results :

Failed tests:   testString(com.google.caliper.memory.ObjectGraphMeasurerTest): 
expected:<Footprint{Objects=3, NonNullRefs=2, NullRefs=0, Primitives=[char x 4, 
int x 3]}> but was:<Footprint{Objects=3, NonNullRefs=2, NullRefs=0, 
Primitives=[int x 2, char x 4]}>

Tests run: 71, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.284s
[INFO] Finished at: Sun Apr 07 22:02:12 EDT 2013
[INFO] Final Memory: 20M/258M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on 
project caliper: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/alex/workspace/caliper/caliper/target/surefire-reports for the individual 
test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

What version of the product are you using? On what operating system?
On a3703ae4544b3952e0944fd8d7e3dcd16f72c3fc

Please provide any additional information below.

Original issue reported on code.google.com by agrothberg on 8 Apr 2013 at 2:04

[GoogleCodeExporter]

Ah yes.  This.  I'm probably just going to have to remove the test.  The idea 
was that String was stable enough to not have to worry about its memory 
footprint changing.  Well, they changed it.

Original comment by gak@google.com on 8 Apr 2013 at 10:00

[GoogleCodeExporter]

Original comment by gak@google.com on 8 Apr 2013 at 10:01

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by gak@google.com on 8 Apr 2013 at 11:09

• Changed state: Fixed