Re: Timer errors in last few days (bignump change?)

[Kaushal Modi]

On Wed, Sep 5, 2018, 6:34 PM Paul Eggert <address@hidden> wrote:

Kaushal Modi wrote:

(63065 20560) corresponds to 2100-12-21 05:00:00 UTC, which is pretty far in the
future, and it seems unlikely you'd want to set alarms for that timestamp.

Oh, thank you! I inadvertently played some "Back from the Future" while hacking with a package test suite to fake the current-time. 

Sorry for your wasted time. It was my mistake.. I redefined current-time. 

--

Kaushal Modi