Commands::Rspec does not catch single rspec failure #54
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
kowal
changed the title
|
@kowal Please rebase to one commit message. |
kowal
force-pushed
the
rspec_failures
branch
2 times, most recently
from
fd22e07
to
911de1b
Compare
|
@nijikon done |
|
@kowal Please add an entry to CHANGELOG |
kowal
force-pushed
the
rspec_failures
branch
2 times, most recently
from
2e39924
to
5bd3ab4
Compare
|
@nijikon I've updated changelog. |
|
@nijikon thanks |
|
I will release new version today. |
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.
Commands::Rspecdoes not catch single rspec failure o_OAlso I've fixed
Tempfile.newusage for Ruby 2.2.4. Without that change CI was failing withArgumentError: wrong number of arguments (0 for 1..2).