tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Temporal: Fix assertion message about float64-representable integer 

This test isn't testing what the assertion message previously said it was
testing. The integer is allowed to be unsafe, but in this case its
float64-representation is out of range.

See: https://github.com/tc39/proposal-temporal/issues/2785
This commit is contained in:
Philip Chimento 2024-02-23 17:58:22 -08:00 committed by Ms2ger
parent c4f5778671
commit f03883c7bb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/built-ins/Temporal/Duration/prototype/round/out-of-range-when-converting-from-normalized-duration.js vendored
View File

@ -13,4 +13,4 @@ const d = new Temporal.Duration(0, 0, 0, 0, 0, 0, /* s = */ Number.MAX_SAFE_INTE
assert.throws(RangeError, () => d.round({ assert.throws(RangeError, () => d.round({
largestUnit: "nanoseconds", largestUnit: "nanoseconds",
roundingIncrement: 1, roundingIncrement: 1,
}), "nanoseconds component is an unsafe integer after balancing"); }), "nanoseconds component after balancing as a float64-representable integer is out of range");