Open Bug 1275716 Opened 3 years ago Updated 2 years ago
_newtab _user Typed Value .js | application timed out after 330 seconds with no output
Where's ma log? No, I mean, seriously, what's going on with the logfile? Why is there nothing in it from the test running? I thought we were supposed to be dumping information for tests that failed? :-\ --> chmanchester, any idea? FWIW, this seems like it's almost certainly related to my attempt to fix bug 1271821. But the logs there all seemed to point to the test timing out at the point of finishing: 18:26:02 INFO - 263 INFO TEST-PASS | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | Should have a closed window - 18:26:02 INFO - 264 INFO TEST-PASS | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | URL bar should be empty - 18:26:02 INFO - 265 INFO TEST-PASS | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | userTypedValue should be null - 18:26:02 INFO - 266 INFO TEST-PASS | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | userTypedValue should be undefined on the tab's state - 18:26:02 INFO - 267 INFO Removing tab - Mon May 23 2016 18:25:55 GMT-0700 (PDT) 18:26:02 INFO - 268 INFO Finished removing tab - Mon May 23 2016 18:25:55 GMT-0700 (PDT) 18:26:02 INFO - 269 INFO Removing window - Mon May 23 2016 18:25:55 GMT-0700 (PDT) 18:26:02 INFO - 270 INFO Finished removing window - Mon May 23 2016 18:25:58 GMT-0700 (PDT) 18:26:02 INFO - 271 INFO Leaving test bound 18:26:02 INFO - 272 INFO TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - https://treeherder.mozilla.org/logviewer.html#?repo=fx-team&job_id=9481064#L15592 FWIW, I do not understand why the test is quite so slow. So Mike, if you have ideas about that with your newfound sessionstore expertise, that would be helpful...
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(cmanchester)
The relevant log from comment 0 is: 08:47:23 INFO - 218 INFO TEST-START | browser/components/sessionstore/test/browser_newtab_userTypedValue.js 08:52:53 INFO - 219 INFO checking window state 08:52:53 INFO - 220 INFO Entering test bound 08:52:53 WARNING - TEST-UNEXPECTED-TIMEOUT | browser/components/sessionstore/test/browser_newtab_userTypedValue.js | application timed out after 330 seconds with no output 5.5 minutes passed without the harness seeing output, so it declared failure and dumped all the output it saw so far (which would explain why the last three lines have the same timestamp). In other words, if we take it at face value, the log is consistent with a hang shortly after starting the test.
The other bug hasn't seen any reoccurrences since the fix there landed, and this one hasn't really either according to brass stacks... so leaving this all be for now.
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.