Closed Bug 1366267 Opened 9 years ago Closed 8 years ago

Intermittent dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js | Test timed out -

Categories

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

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [domsecurity-intermittent][stockwell unknown])

Priority: -- → P3
Whiteboard: [domsecurity-intermittent]
this started failing 10+ times/day on June 12th, primarily win7 opt, in e10s mode. here is a recent log: https://treeherder.mozilla.org/logviewer.html#?repo=try&job_id=107698826&lineNumber=5314 and a related screenshot: http://mozilla-releng-blobs.s3.amazonaws.com/blobs/try/sha512/5da31fffab74abb9f24fbe273e3e7292448338750f96d65b59be6c99f4fef85f9d3ae48b78c58c6558983a2e843e75f833cd0462619fb445814d64bb3454d0aa and inside of the log above, I see: 07:35:45 INFO - TEST-START | dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js 07:36:30 INFO - TEST-INFO | started process screenshot 07:36:31 INFO - TEST-INFO | screenshot: exit 0 07:36:31 INFO - Buffered messages logged at 07:35:45 07:36:31 INFO - Entering test bound 07:36:31 INFO - Buffered messages logged at 07:35:46 07:36:31 INFO - TEST-PASS | dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js | HSTS priming block_active:non-standard-port expected blocked, got blocked - 07:36:31 INFO - Console message: [JavaScript Error: "Blocked loading mixed active content “http://test1.example.com:1234/browser/dom/security/test/hsts/file_testserver.sjs?file=browser/dom/security/test/hsts/file_priming.js&primer=non-standard-port&mimetype=text/javascript&timeout=0”" {file: "https://example.com/browser/dom/security/test/hsts/file_priming-top.html?host=test1.example.com%3A1234&id=non-standard-port&type=script&timeout=0" line: 62}] 07:36:31 INFO - Console message: [JavaScript Warning: "Loading failed for the <script> with source “http://test1.example.com:1234/browser/dom/security/test/hsts/file_testserver.sjs?file=browser/dom/security/test/hsts/file_priming.js&primer=non-standard-port&mimetype=text/javascript&timeout=0”." {file: "https://example.com/browser/dom/security/test/hsts/file_priming-top.html?host=test1.example.com%3A1234&id=non-standard-port&type=script&timeout=0" line: 1}] 07:36:31 INFO - Console message: [JavaScript Error: "Blocked loading mixed active content “http://test1.example.com/browser/dom/security/test/hsts/file_testserver.sjs?file=browser/dom/security/test/hsts/file_priming.js&primer=prime-hsts&mimetype=text/javascript&timeout=0”" {file: "https://example.com/browser/dom/security/test/hsts/file_priming-top.html?host=test1.example.com&id=prime-hsts&type=script&timeout=0" line: 62}] 07:36:31 INFO - Buffered messages finished 07:36:31 INFO - TEST-UNEXPECTED-FAIL | dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js | Test timed out - 07:36:31 INFO - GECKO(6064) | MEMORY STAT | vsize 676MB | vsizeMaxContiguous 724MB | residentFast 202MB | heapAllocated 81MB 07:36:31 INFO - TEST-OK | dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js | took 45041ms 07:36:31 INFO - Not taking screenshot here: see the one that was previously logged 07:36:31 INFO - TEST-UNEXPECTED-FAIL | dom/security/test/hsts/browser_hsts-priming_no-non-standard-ports.js | Found a tab after previous test timed out: https://example.com/browser/dom/security/test/hsts/file_priming-top.html?host=test1.example.com&id=prime-hsts&type=script&timeout=0 - 07:36:31 INFO - checking window state 07:36:31 INFO - TEST-START | dom/security/test/hsts/browser_hsts-priming_timeout.js 07:36:34 INFO - GECKO(6064) | MEMORY STAT | vsize 676MB | vsizeMaxContiguous 724MB | residentFast 205MB | heapAllocated 83MB 07:36:34 INFO - TEST-OK | dom/security/test/hsts/browser_hsts-priming_timeout.js | took 3476ms 07:36:34 INFO - checking window state 07:36:35 INFO - Console message: [JavaScript Warning: "Loading failed for the <script> with source “http://test1.example.com/browser/dom/security/test/hsts/file_testserver.sjs?file=browser/dom/security/test/hsts/file_priming.js&primer=prime-hsts&mimetype=text/javascript&timeout=0”." {file: "https://example.com/browser/dom/security/test/hsts/file_priming-top.html?host=test1.example.com&id=prime-hsts&type=script&timeout=0" line: 1}] 07:36:36 INFO - GECKO(6064) | Completed ShutdownLeaks collections in process 4796 07:36:36 INFO - GECKO(6064) | Completed ShutdownLeaks collections in process 5716 I am doing some retriggers to help narrow this down: https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=e10s%20browser-chrome-4%20win&tochange=b51c4d61a69f8e12386b3caa4632d6c6f64ca2c3&fromchange=3118b9ee9db8f10d53b9352efe3796b917b8930e&selectedJob=106315214 :ckerschb, can you get someone from the dom security team to address this intermittent next week?
Flags: needinfo?(ckerschb)
Whiteboard: [domsecurity-intermittent] → [domsecurity-intermittent][stockwell needswork]
(In reply to Joel Maher ( :jmaher) from comment #3) > :ckerschb, can you get someone from the dom security team to address this > intermittent next week? Kate, can you take a look please?
Flags: needinfo?(ckerschb) → needinfo?(kmckinley)
given the retriggers: https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=e10s%20browser-chrome-4%20win&tochange=b51c4d61a69f8e12386b3caa4632d6c6f64ca2c3&fromchange=3118b9ee9db8f10d53b9352efe3796b917b8930e&selectedJob=107784581 it is really hard to tell if there is a root cause or not, I have 30 data points on a few pushes where 1 shows a failure, but it is only a single failure- that is concerning that I might need many more data points to really make a call on what introduced the failure. It does seem likely that the root cause of this failure is in the above range of commits though.
I think this has reduced in frequency slightly, but I expect we will still have 30+ failures when this week is over- it still should be realistic to reproduce this and work on it.
Kate, any updates on this bug?
Dramatic reduction in failure rate around July 11 (but failures continue).
Whiteboard: [domsecurity-intermittent][stockwell needswork] → [domsecurity-intermittent][stockwell unknown]
Bulk priority update of open intermittent test failure bugs. P3 => P5 https://bugzilla.mozilla.org/show_bug.cgi?id=1381960
Priority: P3 → P5
Flags: needinfo?(kate+bugzilla)
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.