Need help? Watch this RubyConf video
Each CircleCI container now prints out all of the spec files that it ran along with the seed number. If you see a spec that you think might be failing due to an order dependency, you can run rspec <all spec files listed for that container pasted here> --bisect --seed <seed copied from that container pasted here>
locally to get the minimum command to reproduce the failure.
If you run with SSH on CircleCI and need to install VIM on the box to be able to edit specs, follow the 2nd solution on this StackOverflow post to get it installed. You will likely need to use sudo
in front of each of the commands.