Closed
Bug 585396
Opened 14 years ago
Closed 14 years ago
Log how long tests take to run
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla2.0b4
People
(Reporter: mossop, Assigned: mossop)
Details
Attachments
(1 file)
1.91 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
I'm hitting a problem where occasionally some tests of mine are timing out on Windows debug runs. The last time this happened it turned out that the test was just always bordering on the edge of timing out and would just randomly spill over without it being the cause of a problem. To try to figure out if that is the case with the other tests I want to see how long the tests actually take on tinderbox in passing runs. I figured the information would be useful for all tests rather than just mine.
Assignee | ||
Comment 1•14 years ago
|
||
This is a simple patch with just one niggle. Do we mark the start of the test as being when we first load the script, when we call test() or when test() completes and we wait for finish to be called. The latter is most useful for determining whether tests are close to timing out, since this is when the timeout starts, but maybe the full time makes more sense.
Comment 2•14 years ago
|
||
Comment on attachment 463874 [details] [diff] [review] patch rev 1 this looks sufficiently innocuous.
Attachment #463874 -
Flags: review?(gavin.sharp) → review+
Comment 3•14 years ago
|
||
Comment on attachment 463874 [details] [diff] [review] patch rev 1 a=sdwilsh to land on mozilla-central (not that I can set that flag, but you technically need approval I think)
Assignee | ||
Comment 4•14 years ago
|
||
Landed: http://hg.mozilla.org/mozilla-central/rev/3a77b09b6a18
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b4
Updated•6 years ago
|
Component: BrowserTest → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•