darcs

Issue 2068 Apparent bug in match --date

Title Apparent bug in match --date
Priority bug Status given-up
Milestone Resolved in
Superseder Nosy List rpglover64
Assigned To
Topics Regression

Created on 2011-04-23.00:58:21 by rpglover64, last changed 2017-07-31.00:24:57 by gh.

Files
File name Uploaded Type Edit Remove
log rpglover64, 2011-04-23.00:58:19 application/octet-stream
unnamed rpglover64, 2011-05-01.16:04:09 text/html
Messages
msg13954 (view) Author: rpglover64 Date: 2011-04-23.00:58:19
I'm running Snow Leopard on a MacBook Pro.
I have the latest Haskell platform installed, so GHC version 7.0.3.

Attached is the log of running "cabal test match-date", but the relevant
lines seem to be:

| + darcs changes --match 'date "1993-02-04"'
| darcs: Time.toClockTime: picoseconds out of range
Attachments
msg13955 (view) Author: rpglover64 Date: 2011-04-23.00:59:55
BTW, darcs --version gives
2.7.3 (+ 168 patches)
msg13979 (view) Author: kowey Date: 2011-05-01.14:21:02
On Sat, Apr 23, 2011 at 00:58:21 +0000, Alex Rozenshteyn wrote:
> | + darcs changes --match 'date "1993-02-04"'
> | darcs: Time.toClockTime: picoseconds out of range

Hmm, I notice you have this marked as a regression.  Does this
mean you can verify it working properly in an earlier version of
Darcs?  If so, which one?

Thanks,


-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
For a faster response, try +44 (0)1273 64 2905 or
xmpp:kowey@jabber.fr (Jabber or Google Talk only)
msg13980 (view) Author: rpglover64 Date: 2011-05-01.16:04:09
>
> Hmm, I notice you have this marked as a regression.  Does this
> mean you can verify it working properly in an earlier version of
> Darcs?  If so, which one?
>

No; I assumed that at some point it worked. I'm taking that question as an
opportunity to learn how to use "darcs trackdown"
Attachments
History
Date User Action Args
2011-04-23 00:58:21rpglover64create
2011-04-23 00:59:56rpglover64setmessages: + msg13955
2011-05-01 14:21:03koweysetmessages: + msg13979
2011-05-01 16:04:10rpglover64setfiles: + unnamed
messages: + msg13980
2017-07-31 00:24:57ghsetstatus: unknown -> given-up