Conversation
Launchable Report❌ Test session #2825363 failed Passed test sessions✅ Test session #2825347 passed Build: refs_pull_1097_merge_ec352d20ea65c331150d36bc214e196178f619ee |
|
Ruby head is failing because the commit it uses doesn't include the workaround in ruby/irb#919 yet. Once it picks a newer commit it should pass. |
0ebf72f to
aba810f
Compare
When debugging the issue related to ruby/irb#919, I noticed that debugger tests don't respect the IRB version I specified in the Gemfile. This is because console tests force override the RUBYOPT env, which will remove the `-rbundler/setup` injected by bundler. Further more, if tests use `run_rdbg` with the `rubyopt` option, the RUBYOPT will be overridden yet again. So in this commit I did 2 improvements: 1. `run_rdbg` should append instead of override RUBYOPT 2. If tests are executed with bundler, we also run the debugger in PTY process with bundler by appending `-rbundler/setup` to RUBYOPT
aba810f to
ec352d2
Compare
|
Thank you. |
When debugging the issue related to ruby/irb#919, I noticed that debugger tests don't respect the IRB version I specified in the Gemfile. This is because console tests force override the RUBYOPT env, which will remove the
-rbundler/setupinjected by bundler.Additionally, if tests use
run_rdbgwith therubyoptoption, the RUBYOPT will be overridden yet again.So in this commit I did 2 improvements:
run_rdbgshould append instead of override RUBYOPT-rbundler/setupto RUBYOPT