Hi Erich, thanks for trying but it is not sufficient to change the Ticker test 
group, all Windows VMs still hang the test after finalising. What seems to 
block execution is the Ticker built in to the test framework, the thingy that 
goes dot dot dot when the test cases executes. It also does not help to disable 
the ticks using the -u or -U switches. I am quite certain that the Ticker is on 
a separate thread (It can be seen in the task list with a different number) 
would it be possible to trace it using the amended trace that was discussed 
elsewhere?

The change also caused an error in the native Windows (32 and 64 bit) testing, 
I hope you can see what causes the error from this output (the sysdrive error 
is probably a glitch)

ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:        REXX-ooRexx_5.1.0(MT)_32-bit 6.05 6 Apr 2023
OS Name:            WindowsNT
SysVersion:         Windows 10.0.19045

Tests ran:          24152
Assertions:         375095
Failures:           1
Errors:             1

[failure] 20230407 00:53:09.998000
  Test:   TEST_DRIVES
  Class:  SYSDRIVE.TESTGROUP
  File:   ...\ooRexx\base\rexxutil\platform\windows\SysDrive.testGroup
  Line:   116
  Failed: assertTrue
    Expected: 1
    Actual:   0
    Message:  445439692800, 445435510784, SysDriveInfo C: C: 445435510784 
999074459648 Windows; test expected to sometimes fail with a small free space 
delta

[error] 20230407 00:52:35.020000
  Test:   TEST_TICKER_THREE_ARGS_STRING_TRIGGER_MESSAGE
  Class:  Ticker.testGroup
  File:   ...\ooRexx\base\class\Ticker.testGroup
  Event:  SYNTAX 48.1 raised unexpectedly.
    Failure in system service: Ticker Stop SetEvent failure code 6.
    Program: REXX
    Line:    177
       *-* Compiled method "!STOPTIMER" with scope "Ticker".
  1707 *-* Method CANCEL with scope "Ticker" in package "REXX" (no source 
available).
   177 *-* ticker~cancel
       *-* Compiled method "SEND" with scope "Message".
  1585 *-*     .message~new(self, methodName)~send
  1548 *-* self~doTheTest(fName, aTestResult)  -- carry out the testmethod
   552 *-*   test~execute(testResult, verbose)
   552 *-*   test~execute(testResult, verbose)
   110 *-* suite~execute(testResult)
    79 *-* retCode = 'worker.rex'(arguments)

Interpreter:        REXX-ooRexx_5.1.0(MT)_32-bit 6.05 6 Apr 2023
OS Name:            WindowsNT
SysVersion:         Windows 10.0.19045

Tests ran:          24152
Assertions:         375095
Failures:           1
Errors:             1

File search:        00:00:05.017000
Suite construction: 00:00:00.722000
Test execution:     00:05:52.866000
Total time:         00:05:58.606000


jenkins@PO-XPC-FH97 C:\Users\jenkins\workspace\ooRexx-windows32-test>exit 2 
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE

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



> On 6. Apr 2023, at 19:13, Erich Steinböck <erich.steinbo...@gmail.com> wrote:
> 
> I've fixed the Ticker test group to always cancel the Ticker instance even 
> when an assert fails.
> This should fix the hangs.
> _______________________________________________
> 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