Closed Bug 894911 Opened 12 years ago Closed 12 years ago

Take a screenshot when a mochitest-metro-chrome test fails

Categories

(Firefox for Metro Graveyard :: Tests, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jimm, Assigned: jimm)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
I think this would be useful in tracking down intermittent failures.
Attachment #777128 - Flags: review?(sfoster)
Comment on attachment 777128 [details] [diff] [review] patch sorry, wrong patch file.
Attachment #777128 - Attachment is obsolete: true
Attachment #777128 - Flags: review?(sfoster)
Attached patch patchSplinter Review
Assignee: nobody → jmathies
Attachment #777129 - Flags: review?(sfoster)
Comment on attachment 777129 [details] [diff] [review] patch Review of attachment 777129 [details] [diff] [review]: ----------------------------------------------------------------- I'll confess to being slightly dubious about the utility of this, but there's one way to find out; lets land it and see how it plays. Personally, I would usually not want this behavior when testing locally as it fills the terminal buffer and makes it harder to quickly scan over the output (though I see the value of leaving it on by default so you can catch intermittent failures as they happen). I could do that with my own patch to head.js, but some kind of flag or pref would be better
Attachment #777129 - Flags: review?(sfoster) → review+
This would be useful in diagnosing intermittent test failures like bug 896082 but I also don't want to pollute local builds. Need to find a way to only turn this on in automated runs.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: