Closed
Bug 725942
Opened 14 years ago
Closed 14 years ago
mochitest-browser-chrome: browser-test.js should ignore empty console messages
Categories
(Testing :: Mochitest, defect, P4)
Testing
Mochitest
Tracking
(firefox10 wontfix, firefox11 wontfix, firefox12 wontfix, firefox-esr10 wontfix)
VERIFIED
FIXED
mozilla13
People
(Reporter: sgautherie, Assigned: sgautherie)
References
()
Details
Attachments
(1 file)
|
987 bytes,
patch
|
mossop
:
review+
|
Details | Diff | Splinter Review |
While working on SeaMonkey bug 521305, I noticed 2 empty console messages reported by that test.
I ran a Firefox Try build to confirm:
https://tbpl.mozilla.org/?tree=Try&rev=a872216b6fef
90+ empty messages detected
Searching Bugzilla, I find related bug 282253 and bug 564962.
It seems this behavior is +/- a feature and that empty messages should be ignored.
Flags: in-testsuite-
| Assignee | ||
Comment 1•14 years ago
|
||
Attachment #595993 -
Flags: review?
| Assignee | ||
Updated•14 years ago
|
Attachment #595993 -
Flags: review? → review?(dtownsend+bugmail)
Updated•14 years ago
|
Attachment #595993 -
Flags: review?(dtownsend+bugmail) → review+
| Assignee | ||
Comment 2•14 years ago
|
||
Comment on attachment 595993 [details] [diff] [review]
(Av1) browser-test.js: Ignore empty console messages
[Checked in: Comment 2]
https://hg.mozilla.org/mozilla-central/rev/ad0038e0af1f
Attachment #595993 -
Attachment description: (Av1) browser-test.js: Ignore empty console messages → (Av1) browser-test.js: Ignore empty console messages
[Checked in: Comment 2]
| Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•14 years ago
|
||
https://tbpl.mozilla.org/php/getParsedLog.php?id=9337216&tree=Firefox&full=1
Rev3 Fedora 12 mozilla-central opt test mochitest-other on 2012-02-14 14:13:58 PST for push ad0038e0af1f
No more
"TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/browser_sanitizeDialog.js | Console message:"
as an example.
V.Fixed
Status: RESOLVED → VERIFIED
status-firefox-esr10:
--- → affected
status-firefox10:
--- → wontfix
status-firefox11:
--- → wontfix
status-firefox12:
--- → wontfix
Updated•8 years ago
|
Component: BrowserTest → Mochitest
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•