Closed Bug 694457 Opened 14 years ago Closed 14 years ago

jssanity is actually insane

Categories

(Testing Graveyard :: Mozmill, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: k0scist, Unassigned)

Details

https://github.com/mozautomation/mozmill/blob/master/mutt/mutt/tests/js/jssanity.js You'd think that this would have a pass or two, right? Instead the output is: > mozmill -t mutt/mutt/tests/js/jssanity.js Xlib: extension "GLX" missing on display ":0.0". TEST-START | mutt/mutt/tests/js/jssanity.js | setupModule TEST-START | mutt/mutt/tests/js/jssanity.js | testSanity ERROR | Test Failure: {"function": "jum.assertEquals", "comment": "This should fail", "value2": false, "value1": true} INFO | Xlib: extension "GLX" missing on display ":0.0". INFO | INFO | Passed: 0 INFO | Failed: 0 INFO | Skipped: 0 While this doesn't cause mutt to fail, it should probably be fixed.
From irc: 10:18 <@ctalbert> jssanity was old 10:18 <@ctalbert> it was for mutt itself as I recall 10:18 <@ctalbert> since it pre-dates the assertions module the way it does it is likely wrong 10:18 < jhammel> ctalbert: mv -> /dev/null ? 10:20 <@ctalbert> sure, it's just to make sure htat mutt was working when I first wrote it 10:20 < jhammel> ctalbert: coolz, will do So I will remove this
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.