summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-03-21 01:39:56 +0000
committerBundlerbot <bot@bundler.io>2019-03-21 01:39:56 +0000
commitb7de89fa8c1e39251051d26298a902c2630b2e2b (patch)
treed9c8b6beef5fd22b451e9161dad462b4b703efe5
parent6c388a62456912ce8f0898f1c51c22f790356958 (diff)
parent8890cb3d7824d9914717b263bdb4bea65d45954d (diff)
downloadbundler-b7de89fa8c1e39251051d26298a902c2630b2e2b.tar.gz
Merge #7055
7055: Revert the RSpec format in CI back to dots r=colby-swandale a=colby-swandale ### What was the end-user problem that led to this PR? #7017 introduced made a change that sets the RSpec format to `documentation` in CI. I'm against this change because it now takes _a lot_ more time to scroll to the build errors, and makes the build log have too much information. Maintainers care much more about the failing specs and their errors than the test descriptions in CI. ### What is your fix for the problem, implemented in this PR? Explicitly set the RSpec format to `progress` in CI. Co-authored-by: Colby Swandale <me@colby.fyi>
-rw-r--r--Rakefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Rakefile b/Rakefile
index 364ba3ed1f..597564736e 100644
--- a/Rakefile
+++ b/Rakefile
@@ -134,7 +134,7 @@ namespace :spec do
(branches + releases).each do |rg|
desc "Run specs with RubyGems #{rg}"
task rg do
- sh("bin/rspec")
+ sh("bin/rspec --format progress --color")
end
# Create tasks like spec:rubygems:v1.8.3:sudo to run the sudo specs