Closed Bug 674244 Opened 8 years ago Closed 4 years ago

Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 15, 16, 23, 25, 26, 27), expected 5 (or 4, 6)

Categories

(Core :: ImageLib, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mbrubeck, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Beta/1311635022.1311638794.26937.gz
s: talos-r3-fed-043

JavaScript strict warning: resource:///modules/NetworkPrioritizer.jsm, line 117: reference to undefined property aBrowser.webNavigation
TEST-INFO | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Console message: [JavaScript Warning: "reference to undefined property aBrowser.webNavigation" {file: "resource:///modules/NetworkPrioritizer.jsm" line: 117}]
WARNING: NS_ENSURE_TRUE(mState == STATE_TRANSFERRING) failed: file ../../../../netwerk/base/src/nsSocketTransport2.cpp, line 1887
WARNING: 1 sort operation has occurred for the SQL statement '0xa3e2ce0'.  See https://developer.mozilla.org/En/Storage/Warnings details.: file ../../../storage/src/mozStoragePrivateHelpers.cpp, line 144
++DOMWINDOW == 291 (0xf5f5ba8) [serial = 5476] [outer = 0xc9bb4f8]
JavaScript strict warning: chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js, line 143: assignment to undeclared variable chances
TEST-INFO | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Console message: [JavaScript Warning: "assignment to undeclared variable chances" {file: "chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js" line: 143}]
TEST-PASS | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Must have been animating while showing several images
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 26, expected 5
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 26, expected 5
JavaScript strict warning: resource:///modules/NetworkPrioritizer.jsm, line 117: reference to undefined property aBrowser.webNavigation
JavaScript strict warning: resource:///modules/NetworkPrioritizer.jsm, line 117: reference to undefined property aBrowser.webNavigation
JavaScript error: , line 0: uncaught exception: [object StopIteration]
TEST-INFO | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Console message: [JavaScript Warning: "reference to undefined property aBrowser.webNavigation" {file: "resource:///modules/NetworkPrioritizer.jsm" line: 117}]
TEST-INFO | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Console message: [JavaScript Warning: "reference to undefined property aBrowser.webNavigation" {file: "resource:///modules/NetworkPrioritizer.jsm" line: 117}]
INFO TEST-END | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | finished in 14363ms
TEST-INFO | checking window state
TEST-INFO | before wait for focus -- loaded: complete active window: ([object ChromeWindow @ 0xa4ce0f0 (native @ 0xa4cbc28)]) chrome://browser/content/browser.xul focused window: ([object XrayWrapper [object Window @ 0xe83c568 (native @ 0xe94aac8)]]) about:blank desired window: ([object ChromeWindow @ 0xa4ce0f0 (native @ 0xa4cbc28)]) chrome://browser/content/browser.xul child window: ([object XrayWrapper [object Window @ 0xe83c568 (native @ 0xe94aac8)]]) about:blank docshell visible: true
TEST-INFO | already focused
TEST-INFO | maybe run tests <load:true, focus:true> -- loaded: complete active window: ([object ChromeWindow @ 0xa4ce0f0 (native @ 0xa4cbc28)]) chrome://browser/content/browser.xul focused window: ([object XrayWrapper [object Window @ 0xe83c568 (native @ 0xe94aac8)]]) about:blank desired window: ([object ChromeWindow @ 0xa4ce0f0 (native @ 0xa4cbc28)]) chrome://browser/content/browser.xul child window: ([object XrayWrapper [object Window @ 0xe83c568 (native @ 0xe94aac8)]]) about:blank docshell visible: true
TEST-INFO | chrome://mochitests/content/browser/modules/libpr0n/test/browser/browser_image.js | Console message: [JavaScript Error: "uncaught exception: [object StopIteration]"]
TEST-START | chrome://mochitests/content/browser/netwerk/test/browser/browser_NetUtil.js
JS Component Loader: WARNING chrome://mochikit/content/chrome-harness.js:376
                     function readConfig does not always return a value
TEST-INFO | chrome://mochitests/content/browser/netwerk/test/browser/browser_NetUtil.js | Console message: [JavaScript Warning: "function readConfig does not always return a value" {file: "chrome://mochikit/content/chrome-harness.js" line: 376 column: 2 source: "  return JSON.parse(str);
"}]
TEST-PASS | chrome://mochitests/content/browser/netwerk/test/browser/browser_NetUtil.js | request failed
TEST-PASS | chrome://mochitests/content/browser/netwerk/test/browser/browser_NetUtil.js | request is an nsIHttpChannel
TEST-PASS | chrome://mochitests/content/browser/netwerk/test/browser/browser_NetUtil.js | cert error was suppressed
Summary: Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 26, expected 5 → Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 26), expected 5
Version: 6 Branch → Trunk
Summary: Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 26), expected 5 → Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 25, 26), expected 5 (or 6)
Summary: Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 25, 26), expected 5 (or 6) → Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 25, 26, 27), expected 5 (or 6)
Summary: Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 25, 26, 27), expected 5 (or 6) → Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 23, 25, 26, 27), expected 5 (or 6)
Summary: Intermittent TEST-UNEXPECTED-FAIL | libpr0n/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 23, 25, 26, 27), expected 5 (or 6) → Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 23, 25, 26, 27), expected 5 (or 6)
That tightly-spaced wad of fail is from when an unrelated push hit this, then the next push hit this, someone mentioned that so I retriggered on the first push, hit this five more times in a row, backed out that unrelated push which wasn't at all at fault for this, and then retriggered more runs later after I got home from work, every one of which was green, including multiple retriggers on the push where this failed six times in a row.

Is there some sort of a timebomb in this test?
Summary: Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 23, 25, 26, 27), expected 5 (or 6) → Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 15, 23, 25, 26, 27), expected 5 (or 4, 6)
Depends on: 359608
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 15, 23, 25, 26, 27), expected 5 (or 4, 6) → Intermittent TEST-UNEXPECTED-FAIL | image/test/browser/browser_image.js | Sharing the same imgContainer means *exactly* the same frame counts! - Got 24 (or 15, 16, 23, 25, 26, 27), expected 5 (or 4, 6)
Whiteboard: [orange]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(OrangeWFM bugs not touched for 2 months)
Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → WORKSFORME
Seth, this test obviously has something seriously screwy with it given the history of this bug. Instead of going through yet another WORKSFORME->REOPENED->WORKSFORME cycle, can we please either do something to fix this test or just shut it off?
Status: RESOLVED → REOPENED
Flags: needinfo?(seth)
Resolution: WORKSFORME → ---