-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Simplify multiple path support in go plugin #1284
Conversation
…ith spaces in $PATH.
Not sure why the tests failed yet; they pass locally. |
The output is swallowed when run on travis; not sure how to debug.
Any suggestions? |
@nwinkler As you can see, I've tried a bunch of stupid stuff to explore travis and try to make it happy, but I'm completely stumped at this point. the tests pass locally, and they pass on osx. Would you please take a look and tell me what you think? |
Hi, sorry that you have to go through that amount of pain... I was on vacation for the last two weeks. I'll take a look at this in the next couple of days, trying to replicate the issue. I'm running macOS as well, will try a VM for the Linux stuff... |
What's crazy is that the CI says macOS works, and I can say from my testing and experience it works on linux (what I dev on most days). I looked at the ruby plugin tests, but I don't see a meaningful difference in how we are verifying |
Sorry, haven't had time to look into this yet - life got in the way... |
No sweat. That's pretty much my entire last year. |
@nwinkler TRAVIS FINALLY FIXED THE ISSUE AND THE BUILD PASSES. YAAAY!!! |
Woohoo!!!!! Thanks for the patience! (Sorry about the delay, work and life got in the way the last couple of weeks...) |
Likewise! Thanks for your patience as well. |
* simplify wrapped pathmunge logic. update tests to account for cases with spaces in $PATH.
This PR seeks to simplify the wrapped pathmunge logic setup in #1267.
Tests have been updated to account for cases with spaces in $PATH.