Closed Bug 911774 Opened 12 years ago Closed 11 years ago

Intermittent styleinspector/test/browser_ruleview_override.js | Test timed out

Categories

(DevTools :: Inspector, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: intermittent-failure)

Ubuntu VM 12.04 mozilla-inbound pgo test mochitest-browser-chrome on 2013-09-01 23:17:56 PDT for push 85ca556d2bcf slave: tst-linux32-ec2-067 https://tbpl.mozilla.org/php/getParsedLog.php?id=27288432&tree=Mozilla-Inbound { 23:50:17 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Value should be set correctly after re-enabling 23:50:17 INFO - line: background-color: blue; 23:50:17 INFO - line: 23:50:17 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Re-enabling an earlier property shouldn't make it override a later property. 23:50:17 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Rules shouldn't have switched places. 23:50:17 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Rules shouldn't have switched places. 23:50:17 INFO - line: background-color: blue; 23:50:17 INFO - line: 23:50:17 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Modifying an earlier property shouldn't override a later property. 23:50:17 INFO - JavaScript error: resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/styleinspector/rule-view.js, line 1020: this.elementStyle is undefined 23:50:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | Console message: [JavaScript Error: "TypeError: this.elementStyle is undefined" {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/styleinspector/rule-view.js" line: 1020}] 23:50:17 INFO - INFO TEST-END | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_manipulation.js | finished in 1161ms 23:50:17 INFO - TEST-INFO | checking window state 23:50:17 INFO - TEST-START | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_override.js 23:50:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_override.js | Console message: [JavaScript Error: "The character encoding of the HTML 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 page must be declared in the document or in the transfer protocol." {file: "data:text/html,basic%20style%20inspector%20tests" line: 0}] 23:50:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_override.js | Console message: [JavaScript Warning: "XUL box for hbox element contained an inline span child, forcing all its children to be wrapped in a block." {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/inspector/highlighter.js" line: 470}] 23:50:18 INFO - line: 23:50:47 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/styleinspector/test/browser_ruleview_override.js | Test timed out 23:50:47 INFO - INFO | automation.py | Launching: /builds/slave/test/build/tests/bin/screentopng 23:50:47 INFO - Xlib: extension "RANDR" missing on display ":0". }
Blocks: 992211
Mass-closing intermittent-failure bugs filed by me, that have not occurred recently and do not have the leave-open keyword set.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.