Closed Bug 595368 Opened 14 years ago Closed 2 years ago

[test disabled] infinite loop in test_writer_starvation.html

Categories

(Core :: Storage: IndexedDB, defect, P5)

x86
Windows 7
defect

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: dbaron, Assigned: jstutte)

References

Details

(Keywords: intermittent-failure, Whiteboard: [test which aborts the suite][test disabled])

Attachments

(1 file)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1284152312.1284156228.8791.gz
Rev3 WINNT 6.1 mozilla-central opt test mochitests-2/5 [testfailed]

464754 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1
464755 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1
464756 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1
464757 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1
464758 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1

Output exceeded 52428800 bytes, remaining output has been truncated
note that the log snippet was just the very end of a long log.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1284190483.1284194202.16660.gz
Rev3 WINNT 6.1 mozilla-central opt test mochitests-2/5 on 2010/09/11 00:34:43

...
465152 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1
465153 INFO TEST-PASS | /tests/dom/indexedDB/test/test_writer_starvation.html | Correct mode - 1 should equal 1

Output exceeded 52428800 bytes, remaining output has been truncated
program finished with exit code -1073741819
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1292551248.1292556990.11968.gz
Rev3 WINNT 6.1 tracemonkey opt test mochitests-2/5 on 2010/12/16 18:00:48
s: talos-r3-w7-023
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1298266221.1298268474.11639.gz
Rev3 WINNT 5.1 tracemonkey opt test mochitests-2/5 on 2011/02/20 21:30:21
s: talos-r3-xp-040
I presume http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1303244573.1303246739.16523.gz was this, not really sure since it crashed by browser loading the log.
http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1308939557.1308942096.16489.gz

Is this test really valuable enough to be worth the havoc it causes? I'm about one of these enormous logs (which I'm sure are doing wonders for tinderbox's problem with getting through reading its mail, as well as hanging my browser multiple times when I try to load them, and helping to drive me over my connection's cap last month) away from just disabling the test.
yes, I think it's useful, still the loop should have a forced bail out limit even if something goes wrong.
Notice the SQLite upgrade may change things here and we are not too far from that (see also bug 610789).
There might be some more annoying way to fail than by creating 52MB logs, but I can't think what it would be offhand.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7289203&tree=Firefox
Severity: normal → critical
Whiteboard: [orange] → [orange][test which aborts the suite]
https://tbpl.mozilla.org/php/getParsedLog.php?id=7660843&tree=Mozilla-Aurora

Is this test really valuable enough to be worth the havoc it causes?
https://tbpl.mozilla.org/php/getParsedLog.php?id=7772904&tree=Mozilla-Aurora

Is this test really valuable enough to be worth the havoc it causes?
https://tbpl.mozilla.org/php/getParsedLog.php?id=7783021&tree=Mozilla-Inbound

Is this test really valuable enough to be worth the havoc it causes?
https://tbpl.mozilla.org/php/getParsedLog.php?id=7945608&tree=Mozilla-Inbound

Is this test really valuable enough to be worth the havoc it causes?
https://tbpl.mozilla.org/php/getParsedLog.php?id=7964198&tree=Mozilla-Inbound

Is this test really valuable enough to be worth the havoc it causes?
Blocks: 711915
https://tbpl.mozilla.org/php/getParsedLog.php?id=8184512&tree=Mozilla-Inbound

And disabled in https://hg.mozilla.org/integration/mozilla-inbound/rev/0ce4de4491f8 - come back and see us sometime, when you can stop after saying the same thing only a few thousand times.
Summary: infinite loop in test_writer_starvation.html → [test disabled] infinite loop in test_writer_starvation.html
Whiteboard: [orange][test which aborts the suite] → [please leave open][orange][test which aborts the suite]
Whiteboard: [please leave open][orange][test which aborts the suite] → [orange][test which aborts the suite][test disabled]
Whiteboard: [orange][test which aborts the suite][test disabled] → [test which aborts the suite][test disabled]
Priority: -- → P5
Component: DOM → DOM: Core & HTML

Phil does this issue still occur for you or can it be considered closed?

Flags: needinfo?(philringnalda)

The first two words of the summary tell you what the bug is about: "test disabled". The test is still in the tree, and it is still disabled, so the bug is still valid and correctly open, and will be until the test is either removed or fixed and enabled.

Component: DOM: Core & HTML → Storage: IndexedDB
Flags: needinfo?(philringnalda)
QA Whiteboard: qa-not-actionable

So we disabled the test by just removing it from mochitest.ini. We should probably decide, if we want to ever re-enable this (then we should use the disable features of mochitest) or remove it entirely from the tree.

Flags: needinfo?(jvarga)
Assignee: nobody → jstutte
Status: NEW → ASSIGNED

So the test perma-fails now for flaky timeouts. It surely needs some love if it ever shall work again, but for the time being let's just keep track of the disabling.

Flags: needinfo?(jvarga)
Pushed by jstutte@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/79a9d3540889
Explicitly disable test_writer_starvation.html. r=dom-storage-reviewers,janv
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.