我只是在使用 RSpec 测试 Goliath API 时遇到了奇怪的行为。我的一项测试如下所示:
require 'helper'
describe Scales::Dispatch do
it "should return a 404 if resource was not found" do
with_api(Scales::Server) do
get_request(:path => '/') do |client|
client.response_header.http_status.should == 404
end
end
end
it "should return a resource" do
Scales::Storage::Sync.set "/existing", "some content"
with_api(Scales::Server) do
get_request(:path => '/existing') do |client|
client.response_header.http_status.should == 200
client.response.should == "some content"
end
end
Scales::Storage::Sync.del "/existing"
end
end
API 基本上只是借助以下方式在 redis 中查找密钥em-synchrony/em-hiredis
:
module Scales
module Lookup
class << self
def request(env)
response = Storage::Async.get(path(env))
response.nil? ? render_not_found : render(response)
end
private
def path(env)
env["REQUEST_URI"]
end
def render_not_found
[404, {}, ""]
end
def render(response)
[200, {}, response]
end
end
end
end
两个测试单独运行,但不能一起运行。第一个执行后,整个系统会停顿大约 10 秒。然后调用第二个 with_api 但从未执行 get_request - 我认为它正在以某种超时运行。
我在另一个非常相似的测试中发现了相同的行为,该测试正在推送和弹出这样的队列:
describe Scales::Queue::Async do
[Scales::Queue::Async::Request, Scales::Queue::Async::Response].each do |queue|
context queue.name.split("::").last do
it "should place a few jobs" do
async do
queue.add "job 1"
queue.add "job 2"
queue.add "job 3"
end
end
it "should take them out blocking" do
async do
queue.pop.should == "job 1"
queue.pop.should == "job 2"
queue.pop.should == "job 3"
end
end
end
end
end
second 的内容async do ..
也根本不执行。在没有加载 goliath 的情况下,一个非常相似的测试可以完美运行:
require 'eventmachine'
require 'em-synchrony'
require 'em-synchrony/em-hiredis'
module Helpers
def async
if EM.reactor_running?
yield
else
out = nil
EM.synchrony do
out = yield
EM.stop
end
out
end
end
end
RSpec.configure do |config|
config.include Helpers
config.treat_symbols_as_metadata_keys_with_true_values = true
end
describe "em-synchrony/em-hiredis" do
it "should lpush a job" do
async do
redis = EM::Hiredis.connect
redis.lpush("a_queue", "job1")
end
end
it "should block pop a job" do
async do
redis = EM::Hiredis.connect
redis.brpop("a_queue", 0).last.should == "job1"
end
end
end
前面async do ..
的任务是相同的 RSpec 助手。
我整天都在疯狂地寻找,但对我来说这没有任何意义。因为最后一个测试运行得很好,我想它既不是em-synchrony
也不是em-synchrony/em-hiredis
。
也许歌利亚并没有停止,占领新兴市场的时间有点太长了?
感谢您的帮助,这让我发疯了!