browser_586068-reload.js is causing a lot of intermittent failures, and ends up causing even more (often going perma-orange) with patches that affect timing of various things. Given that it's flaky to begin with, and no other tests show problems with these patches, I suspect there's something in the session store code or this test that's subtly timing dependent. I spent a while looking at it and trying different things, and could never find something that fixed it reliably; however, I was also never able to reproduce the failure locally (tried on four different machines over quite a long period). We should just disable this test until someone who understands the session store code can walk through everything and see where things might be going wrong.

Disable this test until we can figure out why it's so fragile.

Comment on attachment 678824 [details] [diff] [review] disable reload test Review of attachment 678824 [details] [diff] [review]: ----------------------------------------------------------------- Sorry for the hassle that this caused. On the positive side, a constantly failing test should be easier to fix :)

True that :) Disabled in https://hg.mozilla.org/integration/mozilla-inbound/rev/bfd200dfc8c3 .