Closed
Bug 1365139
Opened 7 years ago
Closed 7 years ago
Intermittent TEST-UNEXPECTED-TIMEOUT | toolkit/components/places/tests/history/test_removeMany.js | Test timed out
Categories
(Toolkit :: Places, defect, P2)
Toolkit
Places
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: standard8)
Details
(Keywords: intermittent-failure, Whiteboard: [fxsearch])
Attachments
(1 file)
Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=99014249&repo=autoland https://queue.taskcluster.net/v1/task/Qo7vaZ5pRkqPUwjtMcYaGA/runs/0/artifacts/public/logs/live_backing.log
Comment 1•7 years ago
|
||
wow, the test is going a little bit over the top, it starts at 03:13:32 and it's still running sub tests at 03:13:56. It's probably because of const SIZE = 1000; I guess we may want to make the chunklen somehow settable and reduce this to 100... OR make the test not print something on every loop (output slows down tests quite a bit). Mark, could you have a look at this?
Flags: needinfo?(standard8)
Updated•7 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [fxsearch]
Assignee | ||
Comment 3•7 years ago
|
||
Dropping the amount from 1000 -> 400 changes the test time from 16s > 5s on my machine, but will still trigger REMOVE_PAGES_CHUNKLEN. I've commented out one bit of debug as well. That seems a bit more reasonable to me, shall we try it?
Comment hidden (mozreview-request) |
Comment 5•7 years ago
|
||
mozreview-review |
Comment on attachment 8869432 [details] Bug 1365139 - Reduce the amount of iterations for test_removeMany.js so that it takes less time overall to avoid timeouts. https://reviewboard.mozilla.org/r/141068/#review145062 ::: toolkit/components/places/tests/history/test_removeMany.js:12 (Diff revision 1) > "use strict"; > > // Test removing a list of pages > add_task(async function test_remove_many() { > - // This is set so that we are guarenteed to trigger REMOVE_PAGES_CHUNKLEN. > - const SIZE = 1000; > + // This is set so that we are guaranteed to trigger REMOVE_PAGES_CHUNKLEN. > + const SIZE = 400; we could go down to anything above 300 right? so why not 310? ::: toolkit/components/places/tests/history/test_removeMany.js:135 (Diff revision 1) > do_print("Checking out results"); > // By now the observers should have been called. > for (let i = 0; i < pages.length; ++i) { > let page = pages[i]; > - do_print("Page: " + i); > + // do_print("Page: " + i); > Assert.ok(page.onResultCalled, "We have reached the page from the callback"); what about completely removing the do_print and replacing the first Assert message with `We have reached the page #${i} from the callback`
Attachment #8869432 -
Flags: review?(mak77) → review+
Assignee | ||
Comment 6•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8869432 [details] Bug 1365139 - Reduce the amount of iterations for test_removeMany.js so that it takes less time overall to avoid timeouts. https://reviewboard.mozilla.org/r/141068/#review145062 > we could go down to anything above 300 right? so why not 310? Ok, sure. > what about completely removing the do_print and replacing the first Assert message with > `We have reached the page #${i} from the callback` Yeah, nice suggestion, not sure why I didn't think of that.
Comment hidden (mozreview-request) |
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/48965785dc8b Reduce the amount of iterations for test_removeMany.js so that it takes less time overall to avoid timeouts. r=mak
Comment 9•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/48965785dc8b
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•