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
ruby tests failing #41
Comments
See https://travis-ci.org/facebook/watchman/jobs/27038433#L2173 for an example. |
I believe this is caused by the move to RSpec 3.0; I believe we can fix this by specifying a desired RSpec version in the gemspec here: https://github.com/facebook/watchman/blob/master/ruby/ruby-watchman/ruby-watchman.gemspec#L31 (We could also try to tweak the tests so that they pass in RSpec 2.x or 3.x, but that's going to be a game of whack-a-mole, possibly breaking whenever RSpec decides to make upstream changes.) |
These started failing when RSpec 3.0 came out, so adapt the specs to make the tests pass under RSpec 3.0, and peg the dependency to that revision so that we don't have to fix this again in the future. Note that we have to run `bundle install` manually because Travis will only do it for us automatically if it detects a Gemfile in the root level of the repo: http://docs.travis-ci.com/user/languages/ruby/ Sample failure: https://travis-ci.org/facebook/watchman/jobs/29939087 Additionally, ensure we never try a `bundle exec` without first confirming that the `bundle` is present: https://travis-ci.org/facebook/watchman/jobs/29939419 Fixes: #41
looks like we've finally beaten Travis into shape with running the ruby tests here too; closing out. |
I'm going to disable the ruby tests while someone figures out why they're failing.
The text was updated successfully, but these errors were encountered: