Rack-timeout logs are outputed in Rspec's requests specs outputs

[zombocom]

Rack-timeout logs are outputed in Rspec's requests specs outputs

[mariovisic]

You could not require the gem in your test environment, for example in your gemfile add :require => false and then manually require it in an initializer.

Another way (which is how i've done it) is to add this to your spec_helper.rb

# Make rack timeout less noisy in our tests.
Rack::Timeout.logger.formatter = ->(*args) { nil }

Maybe this is something that could be added to the readme?

[kch]

I'll take this into consideration but generally the solution is indeed to change/remove the logger. This will be easier in the next beta, too.

What if I don't log anything for RACK_ENV=test?

[kch]

So now that I've pushed all the nice stuff…

How about:

Rack::Timeout.unregister_state_change_observer(:logger) if ENV['RACK_ENV'] == 'test'

Check out the logging section way down in the readme.

[kch]

@wuputah what's your take here? I kinda don't feel like we should behave differently during tests. What if someone wants to test the log output itself?

The solutions presented above for silencing logs during testing are good enough for me.

[wuputah]

I'm a fan of software being very quiet by default and allowing people to opt-into logging. Perhaps the default logging level be FATAL?

[kch]

This will also likely be fixed by #37 if your test env sends logs to somewhere other than stderr so I'm closing it, but will take it into account for #37.

[kch]

So d1aed68 should address this. For example, if you're using Rails, rack-timeout will log to the rails logger, so when running tests, its logs would end up in logs/test.log.

Otherwise if you wanna remove logging entirely, I refer you back to my comment above.