resque-loner and rspec tests #11

Closed
dkharrat opened this Issue Jul 22, 2011 · 4 comments

Projects

None yet

2 participants

@dkharrat

I'm noticing that the unique keys used to identify jobs are not being removed when running rspec in my app for things that are using resque. I've turned on inline jobs for rspec, which is not supposed to queue them up. Does resque-loner work with inline jobs?

Contributor
jayniz commented Jul 24, 2011

I haven't tried it with the inline jobs - so you're saying that your app's rpsec suite runs jobs inline, and even though they are finished the loner* keys don't get removed from redis? If so, then that's a bug - a pull request would be SWEET :)

Contributor
jayniz commented Aug 4, 2011

pinging @dkharrat

dkharrat commented Aug 4, 2011

I haven't gotten the chance to really investigate it yet. I'll update this issue as soon as I do get the chance to look at it in more detail, and will post results.

Contributor
jayniz commented Aug 5, 2011

Alright, I'll leave it open then. Thanks!

@jayniz jayniz pushed a commit that closed this issue Sep 2, 2011
@arthurdandrea arthurdandrea disable extensions if Resque.inline? fix #11
if Resque.inline? jobs are executed inline (duh) and there is no concurrency, no resque-loner
2aed253
@jayniz jayniz closed this in 2aed253 Sep 2, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment