It's frustrating to need to wait for all the panorama test to run when running tests in browser/base/content that have nothing to do with it. We can pretty easily move the panorama code to browser/components/tabview, I think, which would solve that problem.
Created attachment 564891 [details] [diff] [review]
Created attachment 564893 [details] [diff] [review]
Comment on attachment 564893 [details] [diff] [review]
Review of attachment 564893 [details] [diff] [review]:
Thanks for doing that!
I accidentally also pushed this to inbound:
Let's see what happens!
I backed this out of fx-team, since it also landed on inbound with some minor changes do to a merge requirement:
I think HG fubared the backout with removals+additions :(
mbrubeck pushed a followup to inbound to resolve bustage:
Even after the followup, this is still believed to be the cause of:
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/tabview/test/browser_tabview_bug595518.js | Test timed out
However due to 12 pushes in a row being either red or containing permaoranges, it's not entirely clear what the cause was.
Discussions on #developers between myself, mbrubeck, callek & others, came to the conclusion that we either needed to clean slate hg revert -r last known inbound green (which would have backed this out anyway), or have one last attempt by backing out this bug using hg backout in the hope hg backout wouldn't mess up the renames. The latter was performed using mercurial 1.9.2, but mercurial has unfortunately still not coped with them. The only consolation being that a complete revert to 12+ pushes prior to tip, would have lost the renames regardless.
When this relands, feel free to exclude the tweak you made to bug 689884 if that makes things simpler, since if left it will done by bug 692625 anyway.