Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unittest Failures in AllocationInstrumentTest, ArbitraryMeasurmentInstrumentTest, BadUserCodeTest, RuntimeInstrumentTest #292

Open
GoogleCodeExporter opened this issue May 19, 2015 · 2 comments
Labels
P4 type=defect Bug, not working as expected

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 9 May 2014 at 2:03

Attachments:

@GoogleCodeExporter GoogleCodeExporter added Priority-Medium type=defect Bug, not working as expected labels May 19, 2015
@phishman3579
Copy link

Seeing the same problem, any updates?

@phishman3579
Copy link

I believe I've fixed these problems in my fork. See pull request:
#317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 type=defect Bug, not working as expected
Projects
None yet
Development

No branches or pull requests

4 participants