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

Add note about using the spring-commands-parallel-tests gem to automatically patch and enable Spring #731

Merged
merged 1 commit into from
Dec 7, 2019

Conversation

ndbroadbent
Copy link
Contributor

@ndbroadbent ndbroadbent commented Dec 7, 2019

It took me a while to figure out why I couldn't get Spring to work, so I wanted to add this to the Readme and make it a bit clearer.

See #729 (comment)

EDIT: Actually I've realized that I am able to patch Spring to fix the database issue, and also set the default value of DISABLE_SPRING to "0" in my spring-commands-parallel-tests gem (since this code runs before parallel_tests.) So I might just update the README with instructions to use this gem, if that's ok!

@ndbroadbent ndbroadbent changed the title Added note about default value of DISABLE_SPRING=1, and how you need to force enable Spring with DISABLE_SPRING=0 Add note about using the spring-commands-parallel-rspec gem to automatically patch and enable Spring Dec 7, 2019
@ndbroadbent ndbroadbent changed the title Add note about using the spring-commands-parallel-rspec gem to automatically patch and enable Spring Add note about using the spring-commands-parallel-tests gem to automatically patch and enable Spring Dec 7, 2019
@ndbroadbent ndbroadbent force-pushed the spring_info branch 2 times, most recently from 8303ae3 to 5bac97e Compare December 7, 2019 12:08
Readme.md Outdated Show resolved Hide resolved
@grosser grosser merged commit c8bd00a into grosser:master Dec 7, 2019
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

Successfully merging this pull request may close these issues.

None yet

2 participants