What steps will reproduce the problem?
1. git clone the repository
2. mvn compile
3. mvn package
What is the expected output? What do you see instead?
Expect: Success Got: BUILD FAILURE
Expect: Tests Run: 99, Failures: 0, Errors: 0, Skipped: 0
Got: Tests Run: 99, Failures: 5, Errors: 2, Skipped: 0
After cloning the repository from git, the project builds cleanly, but
packaging it produces 5 Failures and 2 Errors in the unittests:
AllocationInstrumentTest
FAILURE!
intrinsics(com.google.caliper.runner.AllocationInstrumentTest) Time elapsed:
6.032 sec <<< ERROR!
java.util.NoSuchElementException
ArbitraryMeasurmentInstrumentTest
FAILURE!
testSuccess(com.google.caliper.runner.ArbitraryMeasurmentInstrumentTest) Time
elapsed: 0.968 sec <<< ERROR!
java.util.NoSuchElementException
BadUserCodeTest
FAILURE!
testExceptionInMethod_notInDryRun(com.google.caliper.runner.BadUserCodeTest)
Time elapsed: 6.344 sec
<<< FAILURE!
java.lang.AssertionError
testNonDeterministicAllocation_noTrackAllocations(com.google.caliper.runner.BadU
serCodeTest) Time elapsed: 5.553 sec <<< FAILURE!
java.lang.AssertionError
testNonDeterministicAllocation_trackAllocations(com.google.caliper.runner.BadUse
rCodeTest) Time elapsed: 5.536 sec <<< FAILURE!
java.lang.AssertionError
RuntimeInstrumentTest
FAILURE!
gcBeforeEachOptionIsReallyNecessary(com.google.caliper.runner.RuntimeInstrumentT
est) Time elapsed: 0.945 sec <<< FAILURE!
java.lang.AssertionError: No GC warning should be printed to stderr
gcBeforeEachOptionIsHonored(com.google.caliper.runner.RuntimeInstrumentTest)
Time elapsed: 0.94 sec <<< FAILURE!
org.junit.ComparisonFailure: No GC warning should be printed to stderr
expected:<[]> but was:<[ERROR: Trial failed to complete (its results will not
be included in the run):
The worker exited without producing data. It has likely crashed. Run with --verbose to see any worker output.
]>
What version of the product are you using? On what operating system?
Using the HEAD from git, running on Win 7 with JDK 1.7.0_55
Please provide any additional information below.
Original issue reported on code.google.com by joshua.m...@ezxinc.com on 9 May 2014 at 2:03
Original issue reported on code.google.com by
joshua.m...@ezxinc.com
on 9 May 2014 at 2:03Attachments: