dhalperi
commented
9 years ago Fixed, and added some more unit tests so this bug can't creep back in in the future. Have at it!
Also, any sense as to the comparative runtime? Curious if the changes I put in made it faster/use less memory in this case.
i just tried to run 2 queries and both failed after ~ 5 mins because several workers failed in both cases.
queries were 58002 and 58001
is this an issue or are there simply too many jobs being run right now?