Dear Erich,

The Win machine on Jenkins was hanging in the 64 bit test so I aborted it. It 
is building 32 bit now.

There seems to be many different issues at the same time right now, I will do 
some testing as soon as there is a successful build for 12127. These are the 
last lines (the machine was hanging after the last line)

Executing ...\ooRexx\utilities\rxqueue\rxQueue.testGroup
Executing ...\ooRexx\utilities\rxsubcom\rxsubcom.testGroup

ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:        REXX-ooRexx_5.0.0(MT)_64-bit 6.05 19 Nov 2020
OS Name:            WindowsNT
SysVersion:         Windows 10.0.19041

Tests ran:          23995
Assertions:         383986
Failures:           2
Errors:             0

[failure] 20201119 17:37:06.085000
  svn:    r11522   Change date: 2018-11-22 01:34:56 +0100
  Test:   TEST_ERRORTEXT
  Class:  DIGITS.testGroup
  File:   ...\ooRexx\base\bif\DIGITS.testGroup
  Line:   196
  Failed: assertSame
    Expected: Name or string too long.
    Actual:   Name or symbol too long.

[failure] 20201119 17:37:06.086000
  svn:    r11522   Change date: 2018-11-22 01:34:56 +0100
  Test:   TEST_ERRORTEXT
  Class:  ERRORTEXT.testGroup
  File:   ...\ooRexx\base\bif\ERRORTEXT.testGroup
  Line:   92
  Failed: assertSame
    Expected: Name or string too long.
    Actual:   Name or symbol too long.

Interpreter:        REXX-ooRexx_5.0.0(MT)_64-bit 6.05 19 Nov 2020
OS Name:            WindowsNT
SysVersion:         Windows 10.0.19041

Tests ran:          23995
Assertions:         383986
Failures:           2
Errors:             0

File search:        00:00:10.412000
Suite construction: 00:00:01.876000
Test execution:     00:07:30.334000
Total time:         00:07:43.025000

I have the same errors in the macOS builds, but no hang.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 19.11.2020 um 17:59 schrieb Erich Steinböck <erich.steinbo...@gmail.com>:
> 
> With the current trunk we have a hang issue on Windows when running the tests 
> that I cannot track down.
> 
> I have no idea what may have introduced (or surfaced) the issue, and the 
> issue seems elusive as if it were related to GC.
> 
> The fastest way to reproduce is by running
> testoorexx -s -S -f SysFileTree -f Section1
> 
> Help very much appreciated!
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to