Huffington Post translator test seems to intermittently request the same page in an infinite loop about translators

[adam3smith]

I think I replied to the wrong address, so here it goes again:

I'd just leave it disabled - as a test it doesn't seem to work anyway
(locally on scaffold it fails pretty quickly), but I can't find
anything wrong with how the translator works in practice - I listened
in on http traffic while using it and there was nothing unusual - so I
wouldn't know where to start looking for any actual problems. (Also, I
know nothing about the inner workings of the FW - that's Erik's
department).

[simonster]

This is happening again, and I can reproduce it manually at http://www.huffingtonpost.com/business/. The translator repeatedly calls Z.selectItems() and falls into an infinite loop in the test harness if the first item is selected at every step. I'll add guards against this behavior to the harness, so that the translator will just fail instead.

[aurimasv]

Can you still reproduce this manually? It would be very helpful to see the contents of url, the return value of the FW.detectWeb call, and doc.body.innerHTML (other than the actual page that ends up loading last) whenever detectWeb is called. Perhaps you can even make the server testing framework give us these values, since I see that it still fails there.

[aurimasv]

Any idea if this is still an issue? I don't see anything special about Huff Post code, so I would assume that it's either a bug in Framework or the testing harness.