Injecting into inner classes is not supported. Please use a 'static' class (top-level or nested) instead of com.google.caliper.worker.RuntimeWorker$Pico.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run my benchmark in windows, a the 5th trail it always fails with an ex 
exception from Caliper's code. my code is not mentioned on the stack so I am 
guessing it's not really needed to figure out what's wrong.

What is the expected output? What do you see instead?
..

What version of the product are you using? On what operating system?
Windows 7, Caliper commit ac32d3ecb5e8a8cb42bcd41d772da12177ad3def (latest in 
git as of now).

Please provide any additional information below.
This the exception I am getting, I can include the benchmark code if it will 
help.

[trial-5] Exception in thread "main" com.google.inject.CreationException: Guice 
creation errors:
[trial-5] 
[trial-5] 1) Injecting into inner classes is not supported.  Please use a 
'static' class (top-level or nested) instead of 
com.google.caliper.worker.RuntimeWorker$Pico.
[trial-5]   at 
com.google.caliper.worker.WorkerModule.configure(WorkerModule.java:63)
[trial-5] 
[trial-5] 1 error
[trial-5]   at 
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.jav
a:435)
[trial-5]   at 
com.google.inject.internal.InternalInjectorCreator.initializeStatically(Internal
InjectorCreator.java:154)
[trial-5]   at 
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator
.java:106)
[trial-5]   at 
com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:21
7)
[trial-5]   at 
com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:22
4)
[trial-5]     572  49   b   java.lang.StringBuilder::toString (17 bytes)
[trial-5]   at com.google.caliper.worker.WorkerMain.main(WorkerMain.java:42)
The worker exited without producing data. It has likely crashed. Run with 
--verbose to see any worker output.

Original issue reported on code.google.com by o...@yadan.net on 16 Jul 2013 at 6:34

[GoogleCodeExporter]

doing what the error message suggests:
actually solved the problem.

Original comment by o...@yadan.net on 16 Jul 2013 at 7:54

Attachments:

• diff

[GoogleCodeExporter]

Yeah, that was just clearly a bug.  It has already been fixed and I hope to 
push the new code out today (with some other fun changes as well).

Original comment by gak@google.com on 16 Jul 2013 at 5:04

• Changed state: Fixed