This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The last digit seems to be off on the following fn:number tests: fn-numberintg1args-2 The expected result should be 8.309934971170243E17 instead of 8.3099349711702426E17 fn-numberdec1args-2 The expected result should be 6.173751916085148E17 instead of 6.1737519160851482E17 fn-numberflt1args-1 The expected result should be -3.402823466385289E38 instead of -3.4028234663852886E38 fn-numberflt1args-3 The expected result should be 3.402823466385289E38 instead of 3.4028234663852886E38 fn-numberlng1args-2 The expected result should be -4.717556220304846E16 instead of -4.7175562203048464E16 fn-numbernint1args-2 The expected result should be -2.970140759990968E17 instead of -2.9701407599909677E17 fn-numberpint1args-2 The expected result should be 5.270460239061003E16 instead of 5.2704602390610032E16 fn-numberulng1args-2 The expected result should be 1.307471086076747E17 instead of 1.30747108607674656E17 fn-numberulng1args-3 The expected result should be 1.844674407370955E17 instead of 1.8446744073709552E17 fn-numbernpi1args-2 The expected result should be -4.756884372718705E17 instead of -4.7568843727187046E17 fn-numbernni1args-2 The expected result should be 3.038845459914645E17 instead of 3.0388454599146451E17 - Jerome
Jerome: Thanks for the comment. Changed the outcome of some of the test or (as it is our policy) added a second expected outcome, if the test case warrants it. Test cases fn-numbernint1args-2 and fn-numberpint1args-2 were changed to use a different approach. All new changed tests/results were submitted. Please close the bug when able to verify. Thanks, Carmelo