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 tests on Windows I assume it is the counterpart of a segfault on Windows.
Yes, just reported my findings as I can get the crash on the debug version running the test suite with "rexx testOORexx.rex -s -U".
Running the test case individually succeeds with no crash. So it is only in the context of running the entire test suite that this crash occurs while tracing an assignment instruction (when evaluating an expression).
Regarding the notion of “failing” tests on Windows running in Virtual Machines this is the result of the testing framework not finishing (a dangling process) leading to a timeout.
Ah, I see. Would be important to find the cause for that.
All tests normally finish with success you just cannot see it in the Jenkins main screen. This is a candidate for multiple process debugging ;-)
:)
If you look at the 32 and 64 bit Windows running on Native Windows they do not show these problems.
Very good! ---rony _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
