Closed Bug 1585533 Opened 5 years ago Closed 4 years ago

Intermittent fission dom/security/test/csp/test_upgrade_insecure_reporting.html | Test timed out.

Categories

(Core :: DOM: Security, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla76
Fission Milestone M4.1
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: ckerschb)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [domsecurity-active])

Attachments

(2 files)

Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=269358316&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/JQR5NIkdTpOZERv_psjO3w/runs/0/artifacts/public/logs/live_backing.log


[task 2019-10-02T04:03:41.398Z] 04:03:41 INFO - TEST-START | dom/security/test/csp/test_upgrade_insecure_reporting.html
[task 2019-10-02T04:03:42.144Z] 04:03:42 INFO - GECKO(1832) | JavaScript error: resource://gre/modules/LoginManagerContent.jsm, line 874: SecurityError: Permission denied to access property "document" on cross-origin object
[task 2019-10-02T04:08:58.605Z] 04:08:58 INFO - TEST-INFO | started process screentopng
[task 2019-10-02T04:08:58.842Z] 04:08:58 INFO - TEST-INFO | screentopng: exit 0
[task 2019-10-02T04:08:58.843Z] 04:08:58 INFO - Buffered messages logged at 04:03:42
[task 2019-10-02T04:08:58.843Z] 04:08:58 INFO - TEST-PASS | dom/security/test/csp/test_upgrade_insecure_reporting.html | upgraded insecure image load from http -> https
[task 2019-10-02T04:08:58.844Z] 04:08:58 INFO - Buffered messages finished
[task 2019-10-02T04:08:58.844Z] 04:08:58 INFO - TEST-UNEXPECTED-FAIL | dom/security/test/csp/test_upgrade_insecure_reporting.html | Test timed out.
[task 2019-10-02T04:08:58.844Z] 04:08:58 INFO - SimpleTest.ok@SimpleTest/SimpleTest.js:277:18
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - reportError@SimpleTest/TestRunner.js:121:22
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - TestRunner._checkForHangs@SimpleTest/TestRunner.js:142:18
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.845Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.846Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.846Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.846Z] 04:08:58 INFO - setTimeout handlerTestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.846Z] 04:08:58 INFO - setTimeout handler
TestRunner._checkForHangs@SimpleTest/TestRunner.js:170:15
[task 2019-10-02T04:08:58.847Z] 04:08:58 INFO - TestRunner.runTests/<@SimpleTest/TestRunner.js:388:20
[task 2019-10-02T04:08:58.847Z] 04:08:58 INFO - promise callbackTestRunner.runTests@SimpleTest/TestRunner.js:375:50
[task 2019-10-02T04:08:58.847Z] 04:08:58 INFO - RunSet.runtests@SimpleTest/setup.js:201:14
[task 2019-10-02T04:08:58.848Z] 04:08:58 INFO - RunSet.runall@SimpleTest/setup.js:180:12
[task 2019-10-02T04:08:58.848Z] 04:08:58 INFO - hookupTests@SimpleTest/setup.js:273:12
[task 2019-10-02T04:08:58.849Z] 04:08:58 INFO - parseTestManifest@http://mochi.test:8888/manifestLibrary.js:48:13
[task 2019-10-02T04:08:58.849Z] 04:08:58 INFO - getTestManifest/req.onload@http://mochi.test:8888/manifestLibrary.js:61:28
[task 2019-10-02T04:08:58.849Z] 04:08:58 INFO - EventHandlerNonNull
getTestManifest@http://mochi.test:8888/manifestLibrary.js:57:3
[task 2019-10-02T04:08:58.849Z] 04:08:58 INFO - hookup@SimpleTest/setup.js:253:20
[task 2019-10-02T04:08:58.849Z] 04:08:58 INFO - EventHandlerNonNull*@http://mochi.test:8888/tests?autorun=1&closeWhenDone=1&consoleLevel=INFO&manifestFile=tests.json&dumpOutputDirectory=%2Ftmp&cleanupCrashes=true:11:1
[task 2019-10-02T04:08:59.612Z] 04:08:59 INFO - GECKO(1832) | MEMORY STAT | vsize 2552MB | residentFast 130MB | heapAllocated 13MB
[task 2019-10-02T04:08:59.613Z] 04:08:59 INFO - TEST-OK | dom/security/test/csp/test_upgrade_insecure_reporting.html | took 318205ms

Flags: needinfo?(gbrown)
Whiteboard: [domsecurity-intermittent]

So far this appears to be a low-frequency fission-only intermittent test failure. This test was recently un-skipped on fission by bug 1584992.

Flags: needinfo?(gbrown)
Regressed by: 1584992

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?
Fission Milestone: ? → M4.1
Summary: Intermittent fission Tier 2 dom/security/test/csp/test_upgrade_insecure_reporting.html | Test timed out. → Intermittent fission dom/security/test/csp/test_upgrade_insecure_reporting.html | Test timed out.

I'll take a look at this one.

Assignee: nobody → ckerschb
Status: NEW → ASSIGNED
Priority: P5 → P2
Whiteboard: [domsecurity-intermittent] → [domsecurity-active]

A few observations when trying to debug the problem here:

  • 1 failures in 4582; indicates that the problem is almost negligible at this point.
  • Manual inspection of the test does not reveal anything that might obviously be broken because of fission.
  • The logs indicate that the image loading succeeds (grep for "upgraded insecure image load from http -> https" in the logs) which suggests that something around the CSP reporting in the test is broken. My hunch is that the stalled XHR request on the server gets lost before we can report back that the server received the CSP report. I will upload a patch which adds some logging around that. We can leave the bug open for now and next time around the robot posts something on the bug we can investigate those logs.
Keywords: leave-open
Pushed by dvarga@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5cf830ef2611
Add debug statements to fix intermittent test failure on fission for test_upgrade_insecure_reporting.html. r=jkt

Christoph, this rare intermittent Fission test failure hasn't been seen for two months. Can we close this bug as WORKSFORME?

Flags: needinfo?(ckerschb)

(In reply to Chris Peterson [:cpeterson] from comment #18)

Christoph, this rare intermittent Fission test failure hasn't been seen for two months. Can we close this bug as WORKSFORME?

Yes, I just wrote a patch to remove the debug statements. Removing leave-open keyword and this bug will be marked as resolved once the patch for removing the debug statements has landed.

Flags: needinfo?(ckerschb)
Keywords: leave-open
Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c13a7a1fa129
Remove debug statements for test test_upgrade_insecure_reporting.html. r=sstreich
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: