Closed
Bug 950435
Opened 11 years ago
Closed 10 years ago
Intermittent browser_pluginnotification.js | This test exceeded the timeout threshold. It should be rewritten or split up.
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(firefox27 unaffected, firefox28 unaffected, firefox29 fixed, firefox-esr24 unaffected)
RESOLVED
FIXED
mozilla29
Tracking | Status | |
---|---|---|
firefox27 | --- | unaffected |
firefox28 | --- | unaffected |
firefox29 | --- | fixed |
firefox-esr24 | --- | unaffected |
People
(Reporter: philor, Assigned: gfritzsche)
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
11.43 KB,
patch
|
jaws
:
review+
|
Details | Diff | Splinter Review |
https://tbpl.mozilla.org/php/getParsedLog.php?id=31993351&tree=Mozilla-Central WINNT 6.2 mozilla-central debug test mochitest-browser-chrome on 2013-12-14 20:35:32 PST for push c049cb230d77 slave: t-w864-ix-093 20:45:49 INFO - TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/general/browser_pluginnotification.js | Test 27: There should be a plugin notification 20:45:49 INFO - [3808] WARNING: NS_ENSURE_TRUE(mMutable) failed: file c:/builds/moz2_slave/m-cen-w32-d-000000000000000000/build/netwerk/base/src/nsSimpleURI.cpp, line 265 20:45:49 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_pluginnotification.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. 20:45:49 INFO - TEST-INFO | MEMORY STAT vsize after test: 892813312 20:45:49 INFO - TEST-INFO | MEMORY STAT vsizeMaxContiguous after test: 1893662720 20:45:49 INFO - TEST-INFO | MEMORY STAT residentFast after test: 380284928 20:45:49 INFO - INFO TEST-END | chrome://mochitests/content/browser/browser/base/content/test/general/browser_pluginnotification.js | finished in 91160ms
Comment hidden (Legacy TBPL/Treeherder Robot) |
Assignee | ||
Comment 2•11 years ago
|
||
No single step in the logs is taking particularly long, i think that bug 932832 etc just tipped it over the edge. We should break a few of those tests out and definitely not add anything new there.
Priority: -- → P3
Assignee | ||
Comment 3•11 years ago
|
||
Fine on try: https://tbpl.mozilla.org/?tree=Try&rev=0eba696e4789
Assignee: nobody → georg.fritzsche
Attachment #8350606 -
Flags: review?(jaws)
Updated•11 years ago
|
Attachment #8350606 -
Flags: review?(jaws) → review+
Assignee | ||
Comment 4•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a41fa86a7850
Comment 5•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a41fa86a7850
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Updated•10 years ago
|
status-firefox27:
--- → unaffected
status-firefox28:
--- → unaffected
status-firefox29:
--- → fixed
status-firefox-esr24:
--- → unaffected
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•