Time.toClockTime: picoseconds out of range, after diffClockTimes

[Ansible]

I've found a consistent problem where the picoseconds field of TimeDiff? is less than zero. I'm attaching a program that is able to reproduce this problem under 6.8.2.

[Ansible]

This is able to reproduce the bug, at least for me.

[Ansible]

Output from PicoTest?.hs:

*Main> main Welcome to the picotest. Enter 'q' to quit. Hit enter for test:

Clocktime1 1218999538 seconds; 896297000000 picoseconds. Clocktime2 1218999539 seconds; 943780000000 picoseconds. TimeDiff? TimeDiff? {tdYear = 0, tdMonth = 0, tdDay = 0, tdHour = 0, tdMin = 0, tdSec = 1, tdPicosec = 47483000000} converted to seconds: 1.047483 Hit enter for test:

Clocktime1 1218999539 seconds; 946978000000 picoseconds. Clocktime2 1218999540 seconds; 931424000000 picoseconds. TimeDiff? TimeDiff? {tdYear = 0, tdMonth = 0, tdDay = 0, tdHour = 0, tdMin = 0, tdSec = 1, tdPicosec = -15554000000} converted to seconds: *** Exception: Time.toClockTime: picoseconds out of range

[Ansible]

PicoTest?2.hs

[Ansible]

Output from PicoTest?2.hs. Does not produce the bug, although the same ClockTime? values are used.

[1 of 1] Compiling Main ( PicoTest?2.hs, interpreted ) Ok, modules loaded: Main. *Main> main TimeDiff? {tdYear = 0, tdMonth = 0, tdDay = 0, tdHour = 0, tdMin = 0, tdSec = -1, tdPicosec = 15554000000} -0.984446 *Main>

[igloo]

I recommend you use the new time package instead of old-time.

[monoidal]

Closing - the ticket concerns old-time which is abandoned.