Closed
Bug 877824
Opened 11 years ago
Closed 11 years ago
log proper TEST-START and TEST-END points for reftests
Categories
(Testing :: Reftest, defect)
Testing
Reftest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla24
People
(Reporter: froydnj, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
3.54 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•11 years ago
|
||
Reporter | ||
Comment 2•11 years ago
|
||
This is a simple cosmetic change. For parallelizing reftests, we're going to execute subsets of the entire reftest suite and then merge the logs from those subsets. We need some way of identifying that a group of lines belong to a single test so we can keep those lines together in the final merged log. mochitests and xpcshell tests already provide this with TEST-START and TEST-END messages. This patch makes reftests emit the same sort of messages.
Attachment #756168 -
Attachment is obsolete: true
Attachment #756171 -
Flags: review?(dbaron)
Comment on attachment 756171 [details] [diff] [review] log proper TEST-START and TEST-END points for reftests >- gDumpLog("REFTEST TEST-START | Shutdown\n"); >+ gDumpLog("REFTEST INFO | Shutdown\n"); I think this change will probably break some tinderbox consumers, because we depend on bad things that happen during shutdown getting processed into failures that happen in the test "Shutdown" rather than failures that happen in whatever happens to be the last test. r=dbaron if you drop this change or convince me it's not going to break that case
Attachment #756171 -
Flags: review?(dbaron) → review+
Comment 4•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d084b7d0f2e7
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
You need to log in
before you can comment on or make changes to this bug.
Description
•