Closed Bug 960389 Opened 7 years ago Closed 7 years ago

Intermittent WinXP PGO TEST-UNEXPECTED-FAIL | browser_901207_searchbar_in_panel.js | Search container should be overflowing | followed by more customizableui bustage, some timeouts, and finally a crash

Categories

(Firefox :: Toolbars and Customization, defect)

All
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 29
Tracking Status
firefox27 --- unaffected
firefox28 --- unaffected
firefox29 --- affected
firefox-esr24 --- unaffected

People

(Reporter: KWierso, Unassigned)

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=33074987&tree=Mozilla-Central
slave: t-xp32-ix-020



19:33:45     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Entering test
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should be in panel
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | [object HTMLInputElement] (input#.autocomplete-textbox.textbox-input)
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | The searchbar should be focused
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Leaving test
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Entering test
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should be in panel
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | [object HTMLInputElement] (input#.autocomplete-textbox.textbox-input)
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | The searchbar should be focused
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Leaving test
19:33:45     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Entering test
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should start with a non-overflowing toolbar.
19:33:45     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should start in default state.
19:33:45  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Search container should be overflowing
19:33:45     INFO -  Stack trace:
19:33:45     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js :: <TOP_LEVEL> :: line 57
19:33:45     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:33:45     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:33:45     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:33:45     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:06  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Uncaught exception - Panel did not show within 20 seconds.
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Leaving test
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Entering test
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should be in nav-bar
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | [object HTMLInputElement] (input#.autocomplete-textbox.textbox-input)
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | The searchbar should be focused
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Leaving test
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Entering test
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Search container should be in palette
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Search page should be requested to open.
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Should use the current tab for the search page.
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | The search page should have been opened.
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | Leaving test
19:34:06     INFO -  TEST-INFO | MEMORY STAT vsize after test: 568672256
19:34:06     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:06     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 324190208
19:34:06     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 72776068
19:34:06     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_901207_searchbar_in_panel.js | finished in 21353ms
19:34:06     INFO -  TEST-INFO | checking window state
19:34:06     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js
19:34:06     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Entering test
19:34:06  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Should start with a non-overflowing toolbar.
19:34:06     INFO -  Stack trace:
19:34:06     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js :: <TOP_LEVEL> :: line 11
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 261
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:06     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_execTest :: line 571
19:34:06     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_nextTest/< :: line 481
19:34:06     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:06     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Should have an overflowing toolbar.
19:34:06  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Should have fewer children.
19:34:06     INFO -  Stack trace:
19:34:06     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js :: <TOP_LEVEL> :: line 17
19:34:06     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:06     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:06     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:06     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:07     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Other window should have an overflowing toolbar.
19:34:12  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Uncaught exception - Condition timed out: () => !navbar.hasAttribute("overflowing")
19:34:12     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Leaving test
19:34:12     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Entering test asyncCleanup
19:34:12     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | Leaving test asyncCleanup
19:34:12     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567767040
19:34:12     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:12     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 327811072
19:34:12     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 78679442
19:34:12     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_909779_overflow_toolbars_new_window.js | finished in 5625ms
19:34:12     INFO -  TEST-INFO | checking window state
19:34:12     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js
19:34:12     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Entering test
19:34:12  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should start with a non-overflowing toolbar.
19:34:12     INFO -  Stack trace:
19:34:12     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js :: <TOP_LEVEL> :: line 13
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 261
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:12     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_execTest :: line 571
19:34:12     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_nextTest/< :: line 481
19:34:12     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:12     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should start in default state.
19:34:12     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should have an overflowing toolbar.
19:34:12     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Currentset should be the same when overflowing.
19:34:12     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should still be in default state when overflowing.
19:34:12  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should have fewer children.
19:34:12     INFO -  Stack trace:
19:34:12     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js :: <TOP_LEVEL> :: line 21
19:34:12     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:12     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:12     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:12     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:17  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Uncaught exception - Condition timed out: () => !navbar.hasAttribute("overflowing")
19:34:17     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Leaving test
19:34:17     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Entering test
19:34:17     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should start in default state.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should be in default state in customization mode.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Currentset should be the same in customization mode.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Should be in default state after customization mode.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Currentset should be the same after customization mode.
19:34:18     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Leaving test
19:34:18     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Entering test asyncCleanup
19:34:18     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | Leaving test asyncCleanup
19:34:18     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567693312
19:34:18     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:18     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 323592192
19:34:18     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 75674618
19:34:18     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_913972_currentset_overflow.js | finished in 6026ms
19:34:18     INFO -  TEST-INFO | checking window state
19:34:18     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js
19:34:18     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Entering test
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Help button should be disabled while in customization mode.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Quit button should be disabled while in customization mode.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Help button should not be disabled.
19:34:18     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Quit button should not be disabled.
19:34:18     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | Leaving test
19:34:19     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567758848
19:34:19     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:19     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 323878912
19:34:19     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 76836274
19:34:19     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_914863_disabled_help_quit_buttons.js | finished in 588ms
19:34:19     INFO -  TEST-INFO | checking window state
19:34:19     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Entering test
19:34:19     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Should still be in default state
19:34:19     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Should still be in default state
19:34:19  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Should be next to downloads button - Got null, expected wrapper-downloads-button
19:34:19     INFO -  Stack trace:
19:34:19     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: test_is :: line 705
19:34:19     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js :: <TOP_LEVEL> :: line 25
19:34:19     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:19     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:19     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:19     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:19  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Should be next to skipintoolbarset item - Got wrapper-home-button, expected wrapper-test-skipintoolbarset-item
19:34:19     INFO -  Stack trace:
19:34:19     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: test_is :: line 705
19:34:19     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js :: <TOP_LEVEL> :: line 29
19:34:19     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:19     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:19     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:19     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:19     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Should still be in default state
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Leaving test
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Entering test asyncCleanup
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Console message: [JavaScript Error: "IndexSizeError: Index or size is negative or greater than the allowed amount" {file: "resource://app/modules/CustomizeMode.jsm" line: 1028}]
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Console message: [JavaScript Error: "IndexSizeError: Index or size is negative or greater than the allowed amount" {file: "resource://app/modules/CustomizeMode.jsm" line: 1028}]
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | Leaving test asyncCleanup
19:34:19     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567824384
19:34:19     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:19     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 324141056
19:34:19     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 77838880
19:34:19     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_918049_skipintoolbarset_dnd.js | finished in 653ms
19:34:19     INFO -  TEST-INFO | checking window state
19:34:19     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Entering test
19:34:19     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Stuff should exist
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Console message: [JavaScript Error: "IndexSizeError: Index or size is negative or greater than the allowed amount" {file: "resource://app/modules/CustomizeMode.jsm" line: 1028}]
19:34:19     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Console message: [JavaScript Error: "positionManager is undefined" {file: "resource://app/modules/CustomizeMode.jsm" line: 1395}]
19:34:20     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Should be back in default state
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Leaving test
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Entering test asyncCleanup
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | Leaving test asyncCleanup
19:34:20     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567889920
19:34:20     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:20     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 323121152
19:34:20     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 79813958
19:34:20     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_923857_customize_mode_event_wrapping_during_reset.js | finished in 716ms
19:34:20     INFO -  TEST-INFO | checking window state
19:34:20     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Entering test
19:34:20     INFO -  console.error:
19:34:20     INFO -    [CustomizableUI]
19:34:20     INFO -    findWidgetInWindow was passed an empty string.
19:34:20  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Area test-empty-drag should have 1 items. - Got 0, expected 1
19:34:20     INFO -  Stack trace:
19:34:20     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: test_is :: line 705
19:34:20     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/head.js :: placementArraysEqual :: line 83
19:34:20     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/head.js :: assertAreaPlacements :: line 78
19:34:20     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js :: <TOP_LEVEL> :: line 16
19:34:20     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:20     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:20     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:20     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:20  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Button should really be in toolbar
19:34:20     INFO -  Stack trace:
19:34:20     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js :: <TOP_LEVEL> :: line 18
19:34:20     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:20     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:20     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:20     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Console message: [JavaScript Error: "IndexSizeError: Index or size is negative or greater than the allowed amount" {file: "resource://app/modules/CustomizeMode.jsm" line: 1028}]
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Leaving test
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Entering test asyncCleanup
19:34:20     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | Leaving test asyncCleanup
19:34:21     INFO -  TEST-INFO | MEMORY STAT vsize after test: 567889920
19:34:21     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:21     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 323616768
19:34:21     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 81231754
19:34:21     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_927717_customize_drag_empty_toolbar.js | finished in 629ms
19:34:21     INFO -  TEST-INFO | checking window state


Followed later by more:


19:34:23     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_942581_unregisterArea_keeps_placements.js | finished in 76ms
19:34:23     INFO -  TEST-INFO | checking window state
19:34:23     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js
19:34:23     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Entering test
19:34:23  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Button should end up in navbar
19:34:23     INFO -  Stack trace:
19:34:23     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js :: <TOP_LEVEL> :: line 21
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 261
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:23     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_execTest :: line 571
19:34:23     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_nextTest/< :: line 481
19:34:23     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Should have migrated 1 item
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Should have migrated our 1 item
19:34:23  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Second button should end up in the navbar
19:34:23     INFO -  Stack trace:
19:34:23     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js :: <TOP_LEVEL> :: line 27
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 261
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:23     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:23     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_execTest :: line 571
19:34:23     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_nextTest/< :: line 481
19:34:23     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Should have migrated 2 items
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Should have migrated our second item
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Other window should have the same number of migrated items.
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Migrated widget test-addonbar-migration should also be listed as migrated in the other window.
19:34:23     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Migrated widget test-addonbar-migration2 should also be listed as migrated in the other window.
19:34:23     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | Leaving test
19:34:23     INFO -  TEST-INFO | MEMORY STAT vsize after test: 568066048
19:34:23     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:23     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 326365184
19:34:23     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 84338684
19:34:23     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_943683_migration_test.js | finished in 328ms
19:34:23     INFO -  TEST-INFO | checking window state


Followed later by more:


19:34:25     INFO -  TEST-START | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Entering test
19:34:25     INFO -  console.error:
19:34:25     INFO -    [CustomizableUI]
19:34:25     INFO -    Widget 'test-removable-widget-default0' is not removable but does not specify a valid defaultArea. That's not possible; it must specify a valid defaultArea as well.
19:34:25     INFO -  TEST-PASS | unknown test url | Creating non-removable widget without defaultArea should throw.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Should be removable by default.
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Leaving test
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Entering test
19:34:25     INFO -  console.error:
19:34:25     INFO -    [CustomizableUI]
19:34:25     INFO -    Could not localize property 'test-removable-widget-default2.label'.
19:34:25     INFO -  console.error:
19:34:25     INFO -    [CustomizableUI]
19:34:25     INFO -    Could not localize property 'test-removable-widget-default2.tooltiptext'.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be placed.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be in navbar
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should exist in window.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget node should exist in window.
19:34:25  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be in navbar. - Got [object XULElement], expected [object XULElement]
19:34:25     INFO -  Stack trace:
19:34:25     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: test_is :: line 705
19:34:25     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js :: <TOP_LEVEL> :: line 45
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 261
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_handleResultValue :: line 273
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 235
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl :: line 182
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: Task_spawn :: line 152
19:34:25     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_execTest :: line 571
19:34:25     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: Tester_nextTest/< :: line 481
19:34:25     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:25     INFO -  console.error:
19:34:25     INFO -    [CustomizableUI]
19:34:25     INFO -    Could not localize property 'test-removable-widget-default2.label'.
19:34:25     INFO -  console.error:
19:34:25     INFO -    [CustomizableUI]
19:34:25     INFO -    Could not localize property 'test-removable-widget-default2.tooltiptext'.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be placed.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be in navbar
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should exist in other window.
19:34:25     INFO -  TEST-PASS | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget node should exist in other window.
19:34:25  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Widget should be in navbar in other window. - Got [object XULElement], expected [object XULElement]
19:34:25     INFO -  Stack trace:
19:34:25     INFO -      JS frame :: chrome://mochikit/content/browser-test.js :: test_is :: line 705
19:34:25     INFO -      JS frame :: chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js :: <TOP_LEVEL> :: line 59
19:34:25     INFO -      JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 233
19:34:25     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
19:34:25     INFO -      JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
19:34:25     INFO -      native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Leaving test
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Entering test asyncCleanup
19:34:25     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | Leaving test asyncCleanup
19:34:25     INFO -  TEST-INFO | MEMORY STAT vsize after test: 569442304
19:34:25     INFO -  TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 620167168
19:34:25     INFO -  TEST-INFO | MEMORY STAT residentFast after test: 328011776
19:34:25     INFO -  TEST-INFO | MEMORY STAT heapAllocated after test: 90001438
19:34:25     INFO -  INFO TEST-END | chrome://mochitests/content/browser/browser/components/customizableui/test/browser_947987_removable_default.js | finished in 247ms
19:34:25     INFO -  TEST-INFO | checking window state


Then there's several timeouts in:


TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/downloads/test/browser/browser_overflow_anchor.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_drag_bookmarks_on_toolbar.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/search/test/browser_private_search_perwindowpb.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/tabview/test/browser_tabview_bug588265.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/tabview/test/browser_tabview_bug606905.js | Only show button on selected tab. - Got alltabs, expected activetab


And finally there's a crash:



TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_search-basic-02.js | application timed out after 330 seconds with no output
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_search-basic-02.js | application terminated with exit code 3221225477
PROCESS-CRASH | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_search-basic-02.js | application crashed [@ CrashingThread(void *)]
Return code: 1




This is actually a permafail, but apparently only on WinXP PGO runs. I'm triggering PGO builds going back to earlier this morning on m-c to try to figure out when this started happening.
I was originally starring these as bug 947039 for a bit before I realized this was completely separate.
Hrm, fx-team had this PGO failure earlier this morning and it never got starred. Looking there, it was probably one of these five that introduced the failure:

https://tbpl.mozilla.org/?tree=Fx-Team&rev=59251ffa1853
https://tbpl.mozilla.org/?tree=Fx-Team&rev=4ddb7a3d9cae
https://tbpl.mozilla.org/?tree=Fx-Team&rev=7cbf6359300b
https://tbpl.mozilla.org/?tree=Fx-Team&rev=85256e1f3baf
https://tbpl.mozilla.org/?tree=Fx-Team&rev=dad295e99240

I triggered PGO runs for each of these. Lets see where this goes.
backed https://tbpl.mozilla.org/?tree=Fx-Team&rev=dad295e99240 out to see if this fix the issue
Could this be triggered by http://hg.mozilla.org/mozilla-central/rev/77f74253bfbe? This test kind of a mess and fragile by nature... Should we just call resizeTo with an even lower number? But why would this failure be intermittent in the first place?
Flags: needinfo?(jaws)
(In reply to Dão Gottwald [:dao] from comment #8)
> Could this be triggered by
> http://hg.mozilla.org/mozilla-central/rev/77f74253bfbe? This test kind of a
> mess and fragile by nature... Should we just call resizeTo with an even
> lower number? But why would this failure be intermittent in the first place?

Ah, so this actually permanent on WinXP PGO, not happening on Opt and Debug. I have no idea why PGO would cause the "Search container should be overflowing" case to fail. I'd recommend disabling the test until someone understands its behavior. I surely don't.
Can we disable the test for WinPGO only? If that's possible, then we should just do that.
Flags: needinfo?(jaws)
(In reply to Jared Wein [:jaws] from comment #19)
> Can we disable the test for WinPGO only? If that's possible, then we should
> just do that.

Our test harness has no concept of PGO AFAIK. The we can do would be Windows Opt.
(In reply to Jared Wein [:jaws] from comment #19)
> Can we disable the test for WinPGO only? If that's possible, then we should
> just do that.

Not as far as I know, but anyway, since we don't know why this test behaves differently on Windows XP PGO, it seems like the failure could come back randomly in other settings and again cause us to back out innocent patches.
Fixed by backout.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 29
(In reply to Dão Gottwald [:dao] from comment #9)
> (In reply to Dão Gottwald [:dao] from comment #8)
> > Could this be triggered by
> > http://hg.mozilla.org/mozilla-central/rev/77f74253bfbe? This test kind of a
> > mess and fragile by nature... Should we just call resizeTo with an even
> > lower number? But why would this failure be intermittent in the first place?
> 
> Ah, so this actually permanent on WinXP PGO, not happening on Opt and Debug.
> I have no idea why PGO would cause the "Search container should be
> overflowing" case to fail. I'd recommend disabling the test until someone
> understands its behavior. I surely don't.

AFAICT that landing had green PGO runs after it, so it's not that. Seeing as the push I made then perma-oranged it, at least one of them is actually problematic. And because https://tbpl.mozilla.org/?tree=Try&rev=e6ec225174a3 didn't error and https://tbpl.mozilla.org/?tree=Try&rev=e6bc4af89cca did, it's bug 889120's fault. I'll look at what the issue is tomorrow.

Thank you to the sheriffs for the backout. Tomcat: I'm sorry I was snappish about this decision earlier today. Communication-wise, the biggest problem was actually the (otherwise unrelated) bugmail problems today, which meant all the information reached me with about 2 hours delay, in the middle of lots of meetings. That didn't help. In any case, clearly you made the right call. Thank you again. :-)
(In reply to :Gijs Kruitbosch from comment #27)
> (In reply to Dão Gottwald [:dao] from comment #9)
> > (In reply to Dão Gottwald [:dao] from comment #8)
> > > Could this be triggered by
> > > http://hg.mozilla.org/mozilla-central/rev/77f74253bfbe? This test kind of a
> > > mess and fragile by nature... Should we just call resizeTo with an even
> > > lower number? But why would this failure be intermittent in the first place?
> > 
> > Ah, so this actually permanent on WinXP PGO, not happening on Opt and Debug.
> > I have no idea why PGO would cause the "Search container should be
> > overflowing" case to fail. I'd recommend disabling the test until someone
> > understands its behavior. I surely don't.
> 
> AFAICT that landing had green PGO runs after it, so it's not that. Seeing as
> the push I made then perma-oranged it, at least one of them is actually
> problematic. And because https://tbpl.mozilla.org/?tree=Try&rev=e6ec225174a3
> didn't error and https://tbpl.mozilla.org/?tree=Try&rev=e6bc4af89cca did,
> it's bug 889120's fault. I'll look at what the issue is tomorrow.

Nonetheless, it seems suspicious that the part of the test with the magic resizeTo number failed. Of course the other option is that you did indeed break overflowing with your patch. (Only on WinXP PGO...?)
(In reply to Dão Gottwald [:dao] from comment #33)
> (In reply to :Gijs Kruitbosch from comment #27)
> > (In reply to Dão Gottwald [:dao] from comment #9)
> > > (In reply to Dão Gottwald [:dao] from comment #8)
> > > > Could this be triggered by
> > > > http://hg.mozilla.org/mozilla-central/rev/77f74253bfbe? This test kind of a
> > > > mess and fragile by nature... Should we just call resizeTo with an even
> > > > lower number? But why would this failure be intermittent in the first place?
> > > 
> > > Ah, so this actually permanent on WinXP PGO, not happening on Opt and Debug.
> > > I have no idea why PGO would cause the "Search container should be
> > > overflowing" case to fail. I'd recommend disabling the test until someone
> > > understands its behavior. I surely don't.
> > 
> > AFAICT that landing had green PGO runs after it, so it's not that. Seeing as
> > the push I made then perma-oranged it, at least one of them is actually
> > problematic. And because https://tbpl.mozilla.org/?tree=Try&rev=e6ec225174a3
> > didn't error and https://tbpl.mozilla.org/?tree=Try&rev=e6bc4af89cca did,
> > it's bug 889120's fault. I'll look at what the issue is tomorrow.
> 
> Nonetheless, it seems suspicious that the part of the test with the magic
> resizeTo number failed. Of course the other option is that you did indeed
> break overflowing with your patch. (Only on WinXP PGO...?)

Yeah, and it seems now there's intermittent failures on PGO builds as well as occasional opt builds (comment 25).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: Firefox 29 → ---
remote:   https://tbpl.mozilla.org/?tree=Try&rev=d8255af62d5f

So this just reduces the width some more and waits for overflowing to == "true" rather than just hasAttribute, but I'm not too confident it'll actually solve things. The really weird thing about these failures is that if you look at the log timestamps, the toolbar overflows immediately, but somehow the overlay panel doesn't show up and we time out waiting for it.
https://hg.mozilla.org/mozilla-central/rev/5416db3abf30
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 29
You need to log in before you can comment on or make changes to this bug.