Re: strnstr errors in tests while on NetBSD

Hi,

Riccardo Mottola wrote:
> The situation on NetBSD/amd64/libobj2 s now:
>
> 7767 Passed tests
>   46 Failed files
>   32 Dashed hopes
>    8 Failed tests
>
>
> The situation on NetBSD/sparc64/gcc is now:
>
> 9398 Passed tests
>   54 Failed tests
>   46 Dashed hopes
>   14 Skipped sets

On NetBSD/x86-32/gcc I see:

9441 Passed tests
  46 Dashed hopes
  14 Skipped sets
   8 Failed tests


less than SPARC64  but still 8 too many :)

Here some excertps:

Passed test:     basic.m:50 ... call stack addresses is not empty
Passed test:     basic.m:51 ... addresses and symbols match
2021-01-26 12:33:25.181 basic[21435:2832339056] Got ("0: 0xac2a7921
libgnustep-base.so.1.27.0 objc_enumerationMutation + 6663",
 "1: 0x805573a basic __start + 51210", "2: 0x8055a79 basic
gnustep_base_user_main + 823", "3: 0xac447af6 libgnustep-base.so.1.2
7.0 main + 57", "4: 0x8049206 basic __start + 726")
Dashed hope:     basic.m:58 ... working callStackSymbols ... if this has
failed it is probably due to a lack of support for objective-c method
names (local symbols) in the backtrace_symbols() function of your libc.
If so, you might lobby your operating s
ystem provider for a fix.
Passed test:     basic.m:63 ... default handler is null
Passed test:     basic.m:65 ... setting handler works
We expect a single FAIL without any explanation as
the test is terminated by an uncaught exception ...
Passed test:     basic.m:9 ... uncaught exceptionhandler called as expected
/System/Tools/gnustep-tests: line 404: 21435 Abort trap             
(core dumped) $RUN_CMD
Completed file:  basic.m      

Failed test:     general.m:167 ... copy creation date equals original

2021-01-26 12:43:57.083 test07[25421:2963861616] FAILED for unknown
reason possibly not related to the test (e.g. a timer has expired)
Failed test:     test07.m:85 ... HTTPS... big payload... response 400
.... POST https://localhost:1234/400/withoutauth

Failed test:     test00.m:253 ... date check with 2002-03-31 01:30:00
Passed test:     test00.m:258 ... date check with 2002-03-31 00:30:00
Passed test:     test00.m:263 ... date check with 2002-03-31 02:30:00
Failed test:     test00.m:268 ... date check with 2002-03-31 01:30:00
Failed test:     test00.m:272 ... date check with 2002-03-31 00:30:00

hmm several "date" issues then...

Riccardo