One of the big reasons we've used the Obama article to test against is because it's long and complex. Historically, we've had issues that would only surface in particular cases which could often be replicated on highly complex articles, but not necessarily on really simple articles. Is there another article that we could use that meets the criteria of complex and long, but will not cause the 500 errors like Obama article? If so, then let's try that instead. I suspect we do not actually know the answer to this question and worry that we can try finding other workarounds for this problem that will ultimately pile up and cause even more headaches.

The one thing I do know is that we need to do something, and do it soon. If our tests keep failing because of an architectural issue rather an issue in our code, the tests lose their utility - we stop paying attention to failures when they are false positives (or false positive-ish).

Given what I've heard form Antoine and folks in ops, this issue is not likely to be resolved in the near term. Who is the 'owner' of betalabs anyway - ops? platform? QA?

Chris, what do you think we should do to resolve this asap?

 

Antoine, did you have any luck?

 

I think we should either use another article or really fix the issue. Yet another hack feel like it will just introduce further fragility and possibly cause issues with test validity.