Closed portertech closed 9 years ago
Sensu specs are passing, using the Redis transport :+1:
portertech@d2o:~/projects/sensu/sensu (feature/redis-transport *)$ be rake
/home/portertech/.rubies/2.1.2/bin/ruby -I/home/portertech/.gem/ruby/2.1.2/gems/rspec-core-3.0.4/lib:/home/portertech/.gem/ruby/2.1.2/gems/rspec-support-3.0.4/lib -S /home/portertech/.gem/ruby/2.1.2/gems/rspec-core-3.0.4/exe/rspec ./spec/api/process_spec.rb ./spec/cli_spec.rb ./spec/client/process_spec.rb ./spec/client/socket_spec.rb ./spec/daemon_spec.rb ./spec/server/filter_spec.rb ./spec/server/handle_spec.rb ./spec/server/mutate_spec.rb ./spec/server/process_spec.rb ./spec/utilities_spec.rb
{"timestamp":"2015-05-18T22:51:44.824341-0700","level":"fatal","message":"transport connection error","error":"connection closed"}
...........................................................................................................................
Finished in 1 minute 10.06 seconds (files took 0.1808 seconds to load)
123 examples, 0 failures
Ready for review :+1:
It is possible for JIT Redis connection creation to trigger a reconnect, as connected?()
may return false
. Also, the connection monitor is currently enforcing a 3 second timeout :-1:
@grepory :boom:
We're ready for this to make it into a beta build :+1:
Depends on https://github.com/portertech/em-redis/pull/4