Suppress Rspec verbose output #1390
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eugenk
force-pushed
the
disable_rspec_verbosity
branch
from
4829a6f
to
baa47d8
Compare
|
I just rebased on staging (after merging #1392). Hopefully Travis is green now. |
|
One time the output starts with |
|
The specs are executed in a random order. This increases the probability to find erroneous specs (dependent on other specs to run first). |
|
Learning never stops. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the beginning of each run of
rake, the longdb:migrate:cleanoutput as well as the list of the spec files annoyed me a little. This change hides that output. The important things, such as the spec progression and the spec report are still shown.