Closed Bug 1359698 Opened 7 years ago Closed 7 years ago

Intermittent toolkit/components/places/tests/browser/browser_bug399606.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. -

Categories

(Toolkit :: Places, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: bulk-close-intermittents, intermittent-failure)

philor, do we have a bug for these many and annoying "WARNING: file /home/worker/workspace/build/src/ipc/chromium/src/base/histogram.cc, line 637" in the test logs?
it's not the first time I see them, and they seem pointless if nobody cares about them, plus they slowdown logging for sure.
Flags: needinfo?(philringnalda)
00:42:37     INFO - TEST-START | toolkit/components/places/tests/browser/browser_bug399606.js
Then the test starts buffering result messages at 00:42:38 and finishes buffering result messages at 00:44:18.

in the middle there is also:

[task 2017-04-26T00:44:15.617650Z] 00:44:15     INFO - TEST-INFO | started process screentopng
[task 2017-04-26T00:44:18.614591Z] 00:44:18     INFO - TEST-INFO | screentopng: exit 0

I have no idea why this happens after the test started, this way the time needed to start this process seems to be accounted in the test timeout. Matt?
Flags: needinfo?(MattN+bmo)
OK, nevermind, when mozscreenshot runs the test already timed out, to this looks ok. I was confused by the buffered messages.
Flags: needinfo?(MattN+bmo)
The test is reloading 3 times each url for 6 urls. Each refresh is delayed by 1 second, so it's 18 seconds just to wait for the refresh to happen. It's clear this can easily reach the timeout time even if it's not wrong by itself.

It should be possible to split up the test into 2 and test 3 urls per each.
Priority: -- → P3
Found it, bug 1358259.
Flags: needinfo?(philringnalda)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.