-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add csv and logger gems to remove warnings #308
Conversation
9e893cf
to
b2d3405
Compare
20aa43f
to
daafabd
Compare
daafabd
to
e23bbee
Compare
@@ -1,5 +1,10 @@ | |||
# frozen_string_literal: true | |||
|
|||
ENV['RAILS_ENV'] = 'test' | |||
|
|||
$stdout.sync = true |
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.
This is so that if RSpec hangs on Github Action, we see which one.
@@ -22,4 +25,11 @@ | |||
config.expect_with(:rspec) do |c| | |||
c.syntax = %i[should expect] | |||
end | |||
|
|||
config.around do |example| |
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.
All good to have this in spec_helper.rb
and apply to all specs. Even 10 seconds is extremely generous.
|
||
config.around do |example| | ||
# 10 seconds should be more than enough for ANY spec | ||
Timeout.timeout(ENV.fetch('RSPEC_TIMEOUT', 10).to_i) do |
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.
Allow eg CI to override the timeout if necessary.
Fixing two warnings: