Re: failed tests in gnustep-gui

2022-01-18 Thread Andreas Fink 
I usually compile my code in a ssh session. So yes no X.
I started now in X (Remotix helps here as I'm far away) and tests now
run fine.
Now I will look why I never had GUI working on Debian 11.

Sergei Golovin wrote on 18.01.22 11:46:
> On 2022-01-18 14:32:32 +0400 Andreas Fink  wrote:
>
>> 2022-01-18 11:29:42.888 basic[12804:12804] Exception occurred while
>> loading model: Unable to retrieve list of screens from window server.
>>
>> Could it be that the tests fail because I call them from ssh without any
>> X11 active?
>
> Definitely you have no X server around so tests fail
>
> DISPLAY= make check
> ---
>     967 Passed tests
>   8 Failed sets
>   3 Failed tests
> ---
>

Re: failed tests in gnustep-gui

2022-01-18 Thread Andreas Fink 
Running gui/NSNibLoading/basic.m...
Start set:   basic.m:26 ... NSNibLoading GNUstep basic
Passed test: (2022-01-18 11:29:42.884 +0100)   basic.m:44 ...
NSBundle was initialized
2022-01-18 11:29:42.888 basic[12804:12804] Exception occurred while
loading model: Unable to retrieve list of screens from window server.
2022-01-18 11:29:42.888 basic[12804:12804] Failed to load Gorm
Failed test: (2022-01-18 11:29:42.888 +0100)   basic.m:52 ... .gorm
file was loaded properly using loadNibNamed:owner:topLevelObjects:
2022-01-18 11:29:42.898 basic[12804:12804] Exception occurred while
loading model: Unable to retrieve list of screens from window server.
2022-01-18 11:29:42.898 basic[12804:12804] Failed to load Xib
Failed test: (2022-01-18 11:29:42.898 +0100)   basic.m:58 ... .xib
file was loaded properly using loadNibNamed:owner:topLevelObjects:
2022-01-18 11:29:42.939 basic[12804:12804] Exception occurred while
loading model: Unable to retrieve list of screens from window server.
2022-01-18 11:29:42.939 basic[12804:12804] Failed to load Nib
Failed test: (2022-01-18 11:29:42.950 +0100)   basic.m:64 ... .nib
file was loaded properly using loadNibNamed:owner:topLevelObjects:
End set: basic.m:72 ... NSNibLoading GNUstep basic
Completed file:  basic.m


Could it be that the tests fail because I call them from ssh without any
X11 active?

Richard Frith-Macdonald wrote on 18.01.22 09:33:
>
>> On 17 Jan 2022, at 21:15, Andreas Fink  wrote:
>>
>> I get these failures while running gnustep-gui tests:
>>
>> --
>> gui/NSView/NSView_convertRect.m:
>> Failed set:NSView_convertRect.m:100 ... problem in NView GNUstep
>> converRect.
>>
>> gui/NSView/NSView_frame_bounds.m:
>> Failed set:NSView_frame_bounds.m:57 ... problem in NView GNUstep
>> frame_bounds.
>>
>> gui/NSView/NSView_frame_rotation.m:
>> Failed set:NSView_frame_rotation.m:21 ... problem in NView
>> GNUstep frame_rotation.
>>
>> gui/NSView/scrollRectToVisible.m:
>> Failed set:scrollRectToVisible.m:33 ... problem in NView GNUstep
>> scrollRectToVisible.
>> --- Running tests in gui/TextSystem ---
>>
>> 967 Passed tests
>>   8 Failed sets
>>   3 Failed tests
>> 
>>
>>
>> They all fail in a line like this:
>>
>> START_SET("NView GNUstep bounds_scale")
>>
>> So in a macro somwhere.
>> Any idea what this macro does?
> You can just look in the header file (Testing.h) to see exactly what it does, 
> but the summary is that it starts a region of code with an autorelease pool 
> and exception handler and some bookkeeping to track things like the duration 
> of tests.
> Failed set generally means that an exception occurred somewhere in the region 
> betwen the start and the end.  The full log may tell you where/what the 
> exceptionb was.

Re: failed tests in gnustep-gui

2022-01-18 Thread Richard Frith-Macdonald 



> On 17 Jan 2022, at 21:15, Andreas Fink  wrote:
> 
> I get these failures while running gnustep-gui tests:
> 
> --
> gui/NSView/NSView_convertRect.m:
> Failed set:NSView_convertRect.m:100 ... problem in NView GNUstep
> converRect.
> 
> gui/NSView/NSView_frame_bounds.m:
> Failed set:NSView_frame_bounds.m:57 ... problem in NView GNUstep
> frame_bounds.
> 
> gui/NSView/NSView_frame_rotation.m:
> Failed set:NSView_frame_rotation.m:21 ... problem in NView
> GNUstep frame_rotation.
> 
> gui/NSView/scrollRectToVisible.m:
> Failed set:scrollRectToVisible.m:33 ... problem in NView GNUstep
> scrollRectToVisible.
> --- Running tests in gui/TextSystem ---
> 
> 967 Passed tests
>   8 Failed sets
>   3 Failed tests
> 
> 
> 
> They all fail in a line like this:
> 
> START_SET("NView GNUstep bounds_scale")
> 
> So in a macro somwhere.
> Any idea what this macro does?

You can just look in the header file (Testing.h) to see exactly what it does, 
but the summary is that it starts a region of code with an autorelease pool and 
exception handler and some bookkeeping to track things like the duration of 
tests.
Failed set generally means that an exception occurred somewhere in the region 
betwen the start and the end.  The full log may tell you where/what the 
exceptionb was.

Re: failed tests in gnustep-gui

2022-01-17 Thread Sergei Golovin via Discussion list for the GNUstep programming environment 
Andreas Fink  writes:

> I get these failures while running gnustep-gui tests:
>
> --- Running tests in gui/TextSystem ---
>
>     967 Passed tests
>   8 Failed sets
>   3 Failed tests
> 

I currently get on the fresh 'master':

   1000 Passed tests
 2 Dashed hopes

All OK!


Ubuntu 20.04, gcc.

> They all fail in a line like this:
>
>     START_SET("NView GNUstep bounds_scale")
>
> So in a macro somwhere.
> Any idea what this macro does?

It is defined in
   tools-make/TestFramework/Testing.h

-- 
Sergei Golovin