Closed
Bug 431435
Opened 17 years ago
Closed 17 years ago
reftests should report the slowest test
Categories
(Testing :: Reftest, defect)
Testing
Reftest
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Dolske, Assigned: Dolske)
Details
Attachments
(1 file)
|
2.36 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
The reftest timeout has been bumped up in bug 425987 to absurdly high levels. Once those problems are fixes, the timeout should be lowered again.
It would be useful to know what the slowest reftest is during a run (and how long it took). Both for lowering the timeout to normal levels, and for monitoring in the future.
Attachment #318506 -
Flags: review?(dbaron)
Comment on attachment 318506 [details] [diff] [review]
Patch v.1
>+ gSlowestTestURL = gURLs[0]["url" + gState].spec
Terminate with ";" (that's a strict warning, I think?), and r=dbaron.
Attachment #318506 -
Flags: review?(dbaron) → review+
|
Assignee | |
Comment 2•17 years ago
|
||
Oops! Checked in with review nit.
Checking in layout/tools/reftest/reftest.js;
new revision: 1.36; previous revision: 1.35
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9
Component: Testing → Reftest
Product: Core → Testing
Target Milestone: mozilla1.9 → ---
Version: Trunk → unspecified
|
||
Updated•16 years ago
|
QA Contact: testing → reftest
You need to log in
before you can comment on or make changes to this bug.
Description
•