-
Notifications
You must be signed in to change notification settings - Fork 89
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
Validate jvmOpts are passed to forked JVMs properly #33
Comments
Do'h, I meant to use |
😄 Yup, you want // Thanks for the nice report though, if it was a bug that would have been very helpful :-) |
I blame my fat-fingered-ness on the circles I'm circling trying to plug https://github.com/biboudis/jmh-profilers into my profiles. Using the pre-built binary as instructed in the README, I'm unable to get past the "Please unlock commercial features" nag, even though I passed I rebuilt that locally, but then needed to update it some API changes in JMH. But then the generated code still fails to compile with:
But the javac error messages are swallowed. So I'm building |
JMH itself forks JVMs, that's probably the problem - not sure if we're properly passing jvm options to those - probably not. I can look into these things a bit later today, need to look at conductr things now. Let me know if you find anything more so I can continue from where you get to in my evening perhaps. (Reopened and renamed, I hope the title makes sense :-)) |
jmh:version := 0.9
At the top of my problem stack, I think the problem with I set a breakpoint in the spot in SBT where
Removing
I was able to workaround this with: libraryDependencies += "com.github.biboudis" % "jmh-profilers" % "0.1.3-SNAPSHOT" intransitive() |
I was then able to gather the profiling data with:
|
Awesome detective work, thanks a lot @retronym! I'll incorporate those hints and spin a release soon :-) |
I still can't get this working with the binary release of jmh-profilers. There seems to be a forked VM running its code without |
|
See: biboudis/jmh-profilers#4 for the last problem on the stack 😄 |
Great to see that project is active :-) |
This might be something dumb in my environment, but it might also be a mistake in the 0.1,4 release.
😕
The text was updated successfully, but these errors were encountered: