Comment 10 for bug 1754422

The security review is underway. I'm sad that tracking this test case failure down is as complicated as it is -- the code feels overly-generic, tracking call chains through to where anything is *done* is harder than other code bases. Each individual line of code looks fine but getting a handle on the big picture is difficult.

Thanks