-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Updates from rspec-dev (2019-12-18) #2239
Conversation
95166db
to
e237e18
Compare
Closed because this needs tweaking to make it not conflict |
40f81bb
to
f3c6c49
Compare
bf5d9ae
to
4f9100d
Compare
On Bundler 2.1.0 the loading of rubygems has been rewritten. It breaks our existing usage of command execution. The --disable=gem flag is problematic because we need to load rubygems in Bundler. It is not explicitly loaded in Bundle 2.1.0 Related: - rubygems/bundler#7487
26260e4
to
d530d40
Compare
@benoittgt @pirj I think this stands a good chance of going green (its late here so I'm off), its the bare minimum with @benoittgt's rubygems unset and @mvz's bundler patch for Aruba, plus ignoring 4.2.0 (because of bundler 1.x required and we're dropping support anyway) and ignoring a warning on jruby only. 🤞 |
99bb19d
to
00aa976
Compare
in_current_directory do | ||
super(exec_cmd, timeout) | ||
with_unbundled_env do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this call to with_unbundled_env
is not needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, #2244 did not need it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am happy with those changes. Thanks @JonRowe
I merged #2244 in preference as it does less. |
These are some updates, generated from rspec-dev's rake tasks.