Hi all,
There might be more, but these tests fail in Squeak5.2alpha:
DateAndTimeLeapTest>>#testAsSeconds
DoubleWordArrayTest>>#testCannotPutTooLargeValue
UTF16TextConverterTest>>#testByteOrders
UTF16TextConverterTest>>#testByteOrdersWithNonLatin
If someone could have a look at them that would be great!
Best,
Fabio
Hi Levente,
On Wed, 13 Jun 2018 at 14:02, Levente Uzonyi <leves@...> wrote:
>
> On Wed, 13 Jun 2018, Fabio Niephaus wrote:
>
> >
> > Hi all,
> >
> > There might be more, but these tests fail in Squeak5.2alpha:
> >
> > DateAndTimeLeapTest>>#testAsSeconds
>
> If you can answer the question...
On Wed, Jun 13, 2018 at 01:12:05PM +0200, Fabio Niephaus wrote:
> Hi all,
>
> There might be more, but these tests fail in Squeak5.2alpha:
>
> DateAndTimeLeapTest>>#testAsSeconds
> DoubleWordArrayTest>>#testCannotPutTooLargeValue
> UTF16TextConverterTest>>#testByteOrders
> UTF16TextConverterTest...
Hi Alistair,
The everlasting debate is about the time zone. Some say it is UTC, others
say it is whatever time zone you're in. The test is failing, because it
expects the value for UTC, while the method it uses (#asSeconds) was
changed to use your current time zone.
Levente
On Wed, 13 Jun...
... fail in Squeak5.2alpha:
> > >
> > > DateAndTimeLeapTest>>#testAsSeconds
> >
> > If you can answer the question "When the Squeak epoch is?", then this can
> > be fixed.
>
> 1 Jan 1901.
>
> (I haven't looked at the test, I'm battling with file timestamps on
> Windows in the VM at the moment...
On Wed, 13 Jun 2018, Fabio Niephaus wrote:
>
> Hi all,
>
> There might be more, but these tests fail in Squeak5.2alpha:
>
> DateAndTimeLeapTest>>#testAsSeconds
If you can answer the question "When the Squeak epoch is?", then this can
be fixed.
> DoubleWordArrayTest...
...:
> > >>
> > >>On Wed, 13 Jun 2018, Fabio Niephaus wrote:
> > >>>
> > >>> There might be more, but these tests fail in Squeak5.2alpha:
> > >>>
> > >>> DateAndTimeLeapTest>>#testAsSeconds
> > >>
> > >>If you can answer the question "When the Squeak epoch is?", then this
> can
> > >>be fixed.
> > >
> > >1...
...).
> >
>
> The everlasting debate is about the time zone. Some say it is UTC, others
> say it is whatever time zone you're in. The test is failing, because it
> expects the value for UTC, while the method it uses (#asSeconds) was
> changed to use your current time zone.
>
Putting an end to this kind...
Hi Levente,
On Wed, 13 Jun 2018 at 14:34, Levente Uzonyi <leves@...> wrote:
>
> Hi Alistair,
>
> The everlasting debate is about the time zone. Some say it is UTC, others
> say it is whatever time zone you're in. The test is failing, because it
> expects the value for UTC, while the...
On Tue, Jun 19, 2018 at 06:07:07PM -0500, Chris Muller wrote:
> > > The everlasting debate is about the time zone. Some say it is UTC, others
> > > say it is whatever time zone you're in. The test is failing, because it
> > > expects the value for UTC, while the method it uses (#asSeconds) was...
> > The everlasting debate is about the time zone. Some say it is UTC, others
> > say it is whatever time zone you're in. The test is failing, because it
> > expects the value for UTC, while the method it uses (#asSeconds) was
> > changed to use your current time zone.
Right or wrong, the...
Is that a Stack VM? That could explain why it takes more than just a few
minutes to run the full test suite.
Levente
On Fri, 13 Jul 2018, Chris Cunningham wrote:
> Hi.
> I'm trying to run the full test suite in Squeak, and it takes a while. So, I've timed it and noted which parts are...