486640 - Investigate why the browser chrome test for bug 463256 fails intermittently

Status: VERIFIED FIXED

(Firefox :: Private Browsing, defect)

Description

[(no longer active)]

The fix to bug 463256 works, as confirmed manually by me and members of the QA team (Henrik and Marcia, among others).  But the automated test I wrote for it as a browser chrome test fails intermittently both locally and on the try server, therefore I disabled it upon landing the fix for bug 463256.

We need to investigate why this failure happens, and if there is a better way to test this automatically.

The failure seems to be related to the fact that a load request on https://example.com/ never finishes, and just times out.  If the load is canceled and another one is started manually during the test run, everything works correctly.

This may have something to do with the SSL tunnel we use in the mochitest suite, as I have *never* been able to reproduce this failure with a real SSL server (tested with b.m.o, and also on a local SSL Apache web server).

Comment 1

[(no longer active)]

Bug 496335 was fixed.

Comment 2

[Al Billings [:abillings - ex-MoCo]]

Is verifying bug 496335 enough for this?

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/03 - 10/13)]

There was no backout of the latest patch on bug 496335 and even on that bug no-one mentioned any orangeness. So it should be safe to be marked as verified.

Comment 4

[(no longer active)]

The test mentioned in this bug was disabled because of orangeness, and bug 496335 changed the mechanism in that test to make sure that it's robust.  We did not have any orange after that bug landed, so it's indeed safe to mark this as verified.