Mongo-BSON was the package overriding duration. It over-rode duration's
accessor with
duration
^Duration seconds: self asSeconds nanoSeconds: 0
--
View this message in context:
http://forum.world.st/Possible-bug-with-Voyage-Mongo-date-tp4735597p4735638.html
Sent from the Pharo Smallt
For
Date today duration, I got '41281:18:30:00'
and for (Date readFrom: '01-23-2004' readStream) duration: '37641:18:30:00'.
I've loaded only a few packages over the default image
Seaside3(3.1)
VoyageMongo,
JSON
I'm currently looking at the Date class to see if some package overrides any
m
On 10 Jan 2014, at 08:18, raphonic wrote:
> I just ran the entire test suite for Pharo and it seems that the problem
> isn't with voyage or the mongo test driver. The
> DateTest>#testDuration test failed with this message 'Got 37641:18:30:00
> instead of 1:00:00:00'. I'm running the latest phar
I just ran the entire test suite for Pharo and it seems that the problem
isn't with voyage or the mongo test driver. The
DateTest>#testDuration test failed with this message 'Got 37641:18:30:00
instead of 1:00:00:00'. I'm running the latest pharo3.0 vm and image on
Ubuntu 12 x86. Anyone know what
