Closed
Bug 543384
Opened 14 years ago
Closed 14 years ago
Multi-line assertion that makes jsfunfuzz sad
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: n.nethercote)
Details
(Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey, fixed-in-tamarin)
Attachments
(1 file)
3.58 KB,
patch
|
jruderman
:
review+
|
Details | Diff | Splinter Review |
Multi-line assertions like the one in bug 543161 are hard for jsfunfuzz to ignore. The python script that runs jsfunfuzz looks at the output one line at a time. It recognizes anything that starts with "Assertion failure:" as an assertion, but treats it as a known bug if it also matches one of the longer strings in js-known/mozilla-central/assertions.txt. When an assertion message starts with a line break, there's nothing safe to match on and ignore. I guess you could put the extra info in non-assertion output just before the assertion failure. Alternatively, you could put the first line of the message on the first line (don't start with a line break).
Assignee | ||
Comment 1•14 years ago
|
||
This patch makes the assertion messages pithier -- including removing the debugging advice which was probably overkill -- and puts them all on one line.
Attachment #425087 -
Flags: review?(jruderman)
Reporter | ||
Updated•14 years ago
|
Attachment #425087 -
Flags: review?(jruderman) → review+
Assignee | ||
Comment 2•14 years ago
|
||
http://hg.mozilla.org/projects/nanojit-central/rev/42624af80954
Whiteboard: fixed-in-nanojit
Assignee | ||
Comment 3•14 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/2ea76f3022f8
Whiteboard: fixed-in-nanojit → fixed-in-nanojit, fixed-in-tracemonkey
Comment 4•14 years ago
|
||
http://hg.mozilla.org/tamarin-redux/rev/ce413b266124
Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey → fixed-in-nanojit, fixed-in-tracemonkey, fixed-in-tamarin
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/2ea76f3022f8
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•