Hi P.O.,
On 03.04.2024 17:33, ooRexx wrote:
I was imprecise: all Linux/Unix/macOS platforms have a segmentation fault in that group, the test
itself is not failing, but the cause of the segfault must be found and my guess is that it is in
one of your commits?
No, not directly.
As for the
Hi Rony,
I was imprecise: all Linux/Unix/macOS platforms have a segmentation fault in
that group, the test itself is not failing, but the cause of the segfault must
be found and my guess is that it is in one of your commits?
As for the tests on Windows I assume it is the counterpart of a
On 03.04.2024 16:25, ooRexx wrote:
It seems we currently have ALL platforms failing this test, can the person (Rony?) who committed
lately check if there was a side-effect of the changes and/or amend the test to the new behaviour.
Executing
It seems we currently have ALL platforms failing this test, can the person
(Rony?) who committed lately check if there was a side-effect of the changes
and/or amend the test to the new behaviour.
Executing .../ooRexx/base/runtime.objects/environmentEntries.testGroup
Seems more Rexx-ish, unless its specification might conflict with a
future usage of the term in that context.
-Chip-
On 4/2/2024 4:19 PM, Rony wrote:
Another question: offline I got the suggestion to change the NR
entry in TraceObject to NUMBER. What do you think?
