Comment 6 for bug 1427821

Steve Langasek (vorlon) wrote :

In the jenkins automated test at
<>, this error first appears in build 86 on February 19. The test was failing with a different and unrelated error prior to that; it's not clear to me if this is a latent issue that was only exposed once an earlier bug was fixed.