Ok, I have a theory that I'd like you to test out. Run this simple one-line
program after you have killed rxapi, then run it a second time:
say value('RXQUEUESESSION',,'ENVIRONMENT')
I suspect the code gives up trying to connect to the rxapi process
before I has a chance to get fully. The first connection attempt
occurs when it creates the session queue and sets the RXSESSIONQUEUE
env variable. If that never happens, then the rxqueue filter will add
the lines to the wrong session queue.
Rick
On Sun, Dec 2, 2018 at 9:14 AM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:
> I thought I had been clear in my explanation …
>
>
> NO rxapi Running …
>
> Some Rexx scripts run other fail
> The testOORexx script processing the rxQueue.group fails consistently
> Thats why I used it to report the error
>
> The second execution of the same
> Rxapi Running, started by somebody else
> The testOORexx script processing the rxQueue.group ends OK
>
> The full test suite behaves in the same way …
> No rxapi it fails
> Rxapi running it succeeds
>
> That’ what the terminal window paste showed .
>
> To be sure I just rerun the thing …
>
> [enrico@enrico-imac ooRexx.testsuite]$ps -A |grep rxapi
> 13246 ?? 0:00.09 rxapi
> 14041 ttys000 0:00.00 grep rxapi
> [enrico@enrico-imac ooRexx.testsuite]$kill 13246
> [enrico@enrico-imac ooRexx.testsuite]$ps -A |grep rxapi
> 14043 ttys000 0:00.00 grep rxapi
> [enrico@enrico-imac ooRexx.testsuite]$
> [enrico@enrico-imac ooRexx.testsuite]$
> [enrico@enrico-imac ooRexx.testsuite]$rexx testOORexx -s -X native_API
> Searching for test containers...
>
>
> As You see before invoking the test NO rxapi is running
>
> And we get as forecasted the error
>
> ooTest Framework - Automated Test of the ooRexx Interpreter
>
> Interpreter: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Dec 2018
> OS Name: DARWIN
> SysVersion: Darwin Darwin Kernel Version 17.7.0: Wed Oct 10
> 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64.17.7.0
>
> Tests ran: 22398
> Assertions: 375190
> Failures: 4
> Errors: 0
>
> [failure] [20181202 15:01:22.322756]
> svn: r11522 Change date: 2018-11-22 01:34:56 +0100
> Test: TEST_CURRENT_DIR_FILTER
> Class: rxQueue.testGroup
> File: /opt/ooRexx.testsuite/ooRexx/utilities/rxqueue/rxQueue.testGroup
> Line: 89
> Failed: assertSame
> Expected: [[1], identityHash="-4349637953"]
> Actual: [[0], identityHash="-4349603825"]
>
> [failure] [20181202 15:01:22.352226]
> svn: r11522 Change date: 2018-11-22 01:34:56 +0100
> Test: TEST_MULTI_LINES
> Class: rxQueue.testGroup
> File: /opt/ooRexx.testsuite/ooRexx/utilities/rxqueue/rxQueue.testGroup
> Line: 129
> Failed: assertSame
> Expected: [[5], identityHash="-4350538713"]
> Actual: [[0], identityHash="-4349603825"]
>
> [failure] [20181202 15:01:22.381386]
> svn: r11522 Change date: 2018-11-22 01:34:56 +0100
> Test: TEST_RXQUEUE_MAXIMUM_LINE_LENGTH
> Class: rxQueue.testGroup
> File: /opt/ooRexx.testsuite/ooRexx/utilities/rxqueue/rxQueue.testGroup
> Line: 196
> Failed: assertEquals
> Expected: [[2], identityHash="-4349681889"]
> Actual: [[0], identityHash="-4349603825"]
>
> [failure] [20181202 15:01:22.410175]
> svn: r11522 Change date: 2018-11-22 01:34:56 +0100
> Test: TEST_STDERR_TO_RXQUEUE
> Class: rxQueue.testGroup
> File: /opt/ooRexx.testsuite/ooRexx/utilities/rxqueue/rxQueue.testGroup
> Line: 169
> Failed: assertSame
> Expected: [[4], identityHash="-4349990889"]
> Actual: [[0], identityHash="-4349603825"]
>
> Interpreter: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Dec 2018
> OS Name: DARWIN
> SysVersion: Darwin Darwin Kernel Version 17.7.0: Wed Oct 10
> 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64.17.7.0
>
> Tests ran: 22398
> Assertions: 375190
> Failures: 4
> Errors: 0
>
> File search: 00:00:01.246389
> Suite construction: 00:00:01.056062
> Test execution: 00:02:59.653872
> Total time: 00:03:02.227138
>
> [enrico@enrico-imac ooRexx.testsuite]$
>
>
> The error is triggered when the rxapi thing is not there.
>
> But it does not always happen
>
> My point was NOT the failure of the test suite
>
> But the behaviour with respect to rxapi already running or not
>
>
> Hope to have been clear now
>
> cheers
>
> Enrico
>
>
> On 2 Dec 2018, at 14:51, Rick McGuire <object.r...@gmail.com> wrote:
>
> OK, now I'm really confused. This is the opposite of what I was expecting
> to see. I thought it only failed when run as a full suite and passed when
> run alone, but this is showing me the opposite. And the full run is also
> missing the trace lines.
>
>
> _______________________________________________
> 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
