egDate unit test fails on time change boundary

Bug #1671904 reported by Bill Erickson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Low
Unassigned

Bug Description

Evergreen 2.12.

'grunt test' reports:

  egDate
    ✗ should parse a simple interval
        Expected 169200 to be 172800.

The failing test is:

expect(egDate.intervalToSeconds('2 days')).toBe(172800);

==

When crossing time-change boundaries, "2 days" will not be equal to 48-hours worth of seconds. Patch coming that accepts 47, 48, and 49 hours worth of seconds as valid values.

Tags: pullrequest
Revision history for this message
Bill Erickson (berick) wrote :
tags: added: pullrequest
Changed in evergreen:
milestone: none → 2.12-rc
Revision history for this message
Kathy Lussier (klussier) wrote :

Thanks Bill! I tested your branch within the 48 hours that precede the time change, and the karma:unit test succeeded. Merged to master.

Changed in evergreen:
status: New → Fix Committed
importance: Undecided → Low
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.