-
Notifications
You must be signed in to change notification settings - Fork 72
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
Errors when using SeparateJvmsExecutor #231
Comments
See ColOfAbRiX@08cb917 for a possible solution. I'm just removing any classpath that refers to SBT |
After that issue I started receving another exception:
and with a bit of digging it's a known issue with Scala serialization as discussed in this thread scala/bug#9237 I added a new object to deserialize the data in this commit ColOfAbRiX@99d54ae These are quick solutions to the problems and I might not have considered everything. Let me know if you want a PR for those changes or if you think there's more work to do. |
Unfortunately that's not the end of it. While the
creates more problems with different exceptions. |
Same here :( |
My workaround for this is following. |
I'm using Scalameter in a personal project with these versions:
When I use the executor
SeparateJvmsExecutor
I run into a series of problems. The first thing that happens is this exception:This is the custom benchmark I'm using:
Digging into the issue I found that
JvmRunner
includes SBT jars in the classpath, and that creates conflicts.The text was updated successfully, but these errors were encountered: