Closed Bug 1478159 Opened 7 years ago Closed 9 months ago

Intermittent browser/base/content/test/general/browser_bug519216.js | didn't call progressListener4 for the first location change -

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell disabled][retriggered])

Attachments

(1 file)

Filed by: nbeleuzu [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=189893367&repo=mozilla-inbound https://queue.taskcluster.net/v1/task/YUVxQgY3R6KIcPyd0WoL7Q/runs/0/artifacts/public/logs/live_backing.log 13:05:42 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_bug519216.js | didn't call progressListener4 for the first location change - 13:05:42 INFO - Stack trace: 13:05:42 INFO - chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug519216.js:onLocationChange:41 13:05:42 INFO - chrome://browser/content/tabbrowser.js:callListeners:721 13:05:42 INFO - chrome://browser/content/tabbrowser.js:_callProgressListeners:734 13:05:42 INFO - chrome://browser/content/tabbrowser.js:_callProgressListeners:4446 13:05:42 INFO - chrome://browser/content/tabbrowser.js:onLocationChange:4809 13:05:42 INFO - resource://gre/modules/RemoteWebProgress.jsm:_callProgressListeners:144 13:05:42 INFO - resource://gre/modules/RemoteWebProgress.jsm:receiveMessage:237 13:05:42 INFO - MessageListener.receiveMessage*resource://gre/modules/RemoteWebProgress.jsm:swapBrowser:89 13:05:42 INFO - resource://gre/modules/RemoteWebProgress.jsm:RemoteWebProgressManager:72 13:05:42 INFO - chrome://global/content/bindings/remote-browser.xml:remote-browser_XBL_Constructor:413 13:05:42 INFO - chrome://browser/content/tabbrowser.js:_insertBrowser:2016 13:05:42 INFO - chrome://browser/content/tabbrowser.js:addTab:2387 13:05:42 INFO - chrome://mochikit/content/browser-test.js:Tester_waitForWindowsState:578 13:05:42 INFO - chrome://mochikit/content/browser-test.js:nextTest:902 13:05:42 INFO - chrome://mochikit/content/browser-test.js:testScope/test_finish/<:1397 13:05:42 INFO - chrome://mochikit/content/browser-test.js:run:1334 13:05:42 INFO - Console message: [JavaScript Error: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "data:text/plain,bug519216" line: 0}] 13:05:42 INFO - Console message: [JavaScript Error: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "data:text/plain,bug519216" line: 0}]
Hi! Looking at the failure rate of this bug and where it fails I decided to make a patch skipping on all platforms. Could you take a look and see if it's ok? Thank you.
Attachment #9002306 - Flags: review?(jmaher)
Comment on attachment 9002306 [details] [diff] [review] Disable on all platforms Review of attachment 9002306 [details] [diff] [review]: ----------------------------------------------------------------- it looks like this failure started up in the last 5 days as very high frequency- could we find the root cause?
Attachment #9002306 - Flags: review?(jmaher) → review+
this looks hard to track down, but I think on osx or win7 we could find a root cause (treat this like a fresh orange). Eliza could you try that?
Flags: needinfo?(ebalazs)
Justin, FYI- this is a test case that has ownership of firefox::general that we will probably be disabling- not sure if you can find someone to look at this.
Flags: needinfo?(dolske)
Thanks for this work Eliza, there is a lot of good data to look at now. I see that the bc5 job has other very high frequency failures, this is hard to see a pattern by looking at job status. I have a hard time seeing any specific bug as being the root cause when trying to look at failure rates. I think we just need to land the patch to disable the test in this case.
Flags: needinfo?(jmaher)
Whiteboard: [stockwell disable-recommended][retriggered] → [stockwell disabled][retriggered]
Pushed by dluca@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/390c52e04aec Disable browser/base/content/test/general/browser_bug519216.js on all platforms. r=jmaher
Keywords: checkin-needed
Declaring new-year needinfo bankruptcy.
Flags: needinfo?(dolske)
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: