Comment 1 for bug 537950

I'm able to reproduce this error virtually at will. All it takes is to run this test twice in parallel (with spawns). This extra test is now test_multi_window and I'll work on fixing it.

Curious, the error goes away if I simply put a "Sleep 1s" before the SetCurrentWindow in test_window.test (that is, before the one that requires the new window to be open). This may thus be some timing issue we haven't seen. Perhaps selenium isn't waiting, or reporting success when the window isn't yet open.