[inline]

-- 
Tobias Pape
sent from a mobile device

> Am 14.07.2014 um 23:52 schrieb Frank Shearar <frank.shearar at gmail.com>:
> 
>> On 14 July 2014 22:36, Chris Muller <asqueaker at gmail.com> wrote:
>> Why not just cleanly list the name of the failing test and nothing else?
>> Tests are only understood and debugged in the running image, not from a
>> cryptic message reported on the build website.
> 
> I realise that _you_ don't use CI to debug tests. I do. I find value
> in these error messages, especially since I don't have a Linux
> machine, and as it happens, a test (see Tests-fbs.301) fails in
> Spur+Linux but passes in Spur+Windows.

 +1
> 
>> It certainly can't be fixed
>> and committed without running the test in the image anyway.
> 
> Yes, and so what?
> 
>> So why do we want to see that debugging noise in the build-server reports?
> 
> How is a decent error message noise? I find ENORMOUS value in these
> error messages. How could I possibly report a problem on a Linux box
> to Eliot otherwise?
> 
> frank
> 
>> On Mon, Jul 14, 2014 at 4:11 PM, Frank Shearar <frank.shearar at gmail.com>
>> wrote:
>>> 
>>> 
>>> http://build.squeak.org/job/SqueakTrunkOnSpur/31/testReport/junit/KernelTests.Chronology/DateAndTimeTest/testReadFrom/
>>> shows a not-very-helpful test failure report: Expected
>>> '2002-05-1...etc... but was '2002-05-1...etc....
>>> 
>>> If build.squeak.org is anything like my machine, that failure might
>>> more profitably be reported as:
>>> 
>>> Expected '2002-05-16T17:20:00+00:00' but was '2002-05-16T17:20:00+01:00'
>>> 
>>> from this assertion:
>>> 
>>> self assert: '2002-05-16T17:20:00+00:00' equals: ' 2002-05-16T17:20'
>>> asDateAndTime printString.
>>> 
>>> Is this expected (because of changes in datetime primitives)?
>>> 
>>> frank
>