-
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
Enable --verbose
when running specs
#7708
Conversation
Ok. So this did not help reproducing exactly but provided some clues. If I run the command now suggested in the error output, everything still passes. BUT, if I run that command, with my internet connection switched off, then the same set of specs fail, just with a different error message. Well, not exactly the same, I believe some more, but all the specs that fail in CI here also fail without an internet connection. I suspect this is some change in rubygems.org. |
6e44874
to
7c05493
Compare
1243942
to
2ee4125
Compare
1f11807
to
ecd2e80
Compare
--verbose
when running bundler specs--verbose
when running specs
This was not the proper hint, but I think it does not hurt to have 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 don't have a strong opinion on this so I think it's fine to enable verbose output
That prints the actual RSpec command that gets run under the hood, so makes it easier to reproduce and debug a failing "slice".
ecd2e80
to
c4e5456
Compare
I think this is not too invasive, and quite helpful for troubleshooting CI, so let's do it. If somebody finds it too much we can switch back! |
That prints the actual RSpec command that gets run under the hood. If the current CI flakies are order dependent, it should allow us to reproduce them.