From f03883c7bb7ef0aaeca00439e014eccc7b4d7dc5 Mon Sep 17 00:00:00 2001 From: Philip Chimento Date: Fri, 23 Feb 2024 17:58:22 -0800 Subject: [PATCH] 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 --- .../out-of-range-when-converting-from-normalized-duration.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/built-ins/Temporal/Duration/prototype/round/out-of-range-when-converting-from-normalized-duration.js b/test/built-ins/Temporal/Duration/prototype/round/out-of-range-when-converting-from-normalized-duration.js index a6f47963ff..bcac75e573 100644 --- a/test/built-ins/Temporal/Duration/prototype/round/out-of-range-when-converting-from-normalized-duration.js +++ b/test/built-ins/Temporal/Duration/prototype/round/out-of-range-when-converting-from-normalized-duration.js @@ -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({ largestUnit: "nanoseconds", roundingIncrement: 1, -}), "nanoseconds component is an unsafe integer after balancing"); +}), "nanoseconds component after balancing as a float64-representable integer is out of range");