Closed Bug 822188 Opened 12 years ago Closed 12 years ago

Investigate and fix failing non-private browsing tests for new per window private browsing mode

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whimboo, Assigned: AndreeaMatei)

References

Details

(Whiteboard: s=121217 u=failure c=private_browsing p=1)

Beside the actual private browsing tests which are failing at the moment we have seen a couple of other tests which are failing too since the per window private browsing feature has been landed. This bug is mostly a meta bug and will cover all other instances of those failures which have to be fixed as soon as possible.
Assignee: nobody → andreea.matei
Status: NEW → ASSIGNED
Do we have an update here? Why are those tests broken? Is the brokenness related to our broken private browsing tests? If yes, we should figure out how to make them more stable.
This it's not reproducing anymore, they did until December 30th build (from reports), I've tried with those older builds but no luck. From the 14th when all started: * http://mozmill-crowd.blargon7.com/#/functional/report/23d8fbdd0190d4b0496d6b129fb73cd8 And other builds: * http://mozmill-crowd.blargon7.com/#/functional/report/23d8fbdd0190d4b0496d6b129fb5d216 * http://mozmill-crowd.blargon7.com/#/functional/report/23d8fbdd0190d4b0496d6b129fb521c2
Lets keep the bug open until all dependencies have been fixed. If we stay green that would be wonderful.
None of the other non-privatebrowsing tests are failing anymore. Lets get this bug closed.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.