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

Blue-Ridge spawns a new JVM for each test file #30

Open
dmcinnes opened this issue Dec 18, 2009 · 2 comments
Open

Blue-Ridge spawns a new JVM for each test file #30

dmcinnes opened this issue Dec 18, 2009 · 2 comments

Comments

@dmcinnes
Copy link

It would be nice if it could run in a single instance of the JVM since startup time is a big issue.
gleneivey has a branch that did this but it seems his latest merge from relevance/blue-ridge broke that behavior.
Thanks!

@gleneivey
Copy link

Hi. My "test-in-one-jvm" and "local" branches both (still) "work for me". Could you let me know where exactly you pulled from and what changed from "before" to now? -- glen

@dmcinnes
Copy link
Author

Oh I bet I know what went wrong!
We're using braid to hook in the plugin and I think the blue-ridge remote was still pointing to the relevance fork. I couldn't for the life of me pull in an older version of your branch until I removed that remote definition even though I was giving your branch's github URL.

Nice work by the way! It runs way faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants