Closed Bug 1371704 Opened 8 years ago Closed 7 years ago

Permaorange in test_pinning.js on Win8 debug when Gecko 55 merges to beta on 2017-06-12

Categories

(Core :: Security: PSM, defect, P1)

Product:
Core
Component:
Security: PSM
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1370644
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 --- affected

People

(Reporter: RyanVM, Unassigned)

Details

[Tracking Requested - why for this release]: merge bustage, closed tree, delayed b1 Something that landed in the last couple days is going to cause test_pinning.js to permafail when we merge to beta on Monday, but for some reason I can't comprehend, only on Win8 debug. Unless there's an easy test-only fix, we should probably consider backing out the regressing patch at this point to minimize risk to the merge. https://treeherder.mozilla.org/logviewer.html#?job_id=105637913&repo=try
Flags: needinfo?(dkeeler)
Well, looking at that stack trace, there's this: > 16:02:12 INFO - PID 8112 | #06: <lambda_5a2b5c6d24e46eeba8c7c381d7cd37fb>::operator() [netwerk/base/nsSocketTransportService2.cpp:1629] Which points me to https://dxr.mozilla.org/mozilla-central/rev/e61060be36424240058f8bef4c5597f401bc8b7e/netwerk/base/nsSocketTransportService2.cpp#1610 and bug 1370448.
Flags: needinfo?(dkeeler) → needinfo?(ehsan)
I'm taking a look. Please don't back out bug 1370448, a number of stuff depends on it...
marking as blocking 55, as we merge to beta on monday
tracking-firefox55: ? → blocking
The patch in bug 1370644 fixes this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.