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 segfault on 
Windows.

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. 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.

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



> On 3. Apr 2024, at 16:45, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote:
> 
> 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 .../ooRexx/base/runtime.objects/environmentEntries.testGroup
>> /tmp/jenkins3639803152023253797.sh: line 15: 26971 Segmentation fault      
>> (core dumped) rexx testOORexx.rex -s -U
>> Build step 'Execute shell' marked build as failure
>> Finished: FAILURE
>> 
> Looking at Jenkins I do not see that test failing on all systems at all:
> 
> <k5DNTm3UeCM3iJMM.png>
> 
> However, I can see those segmentation faults in some of those tests.
> 
> No idea what causes them.
> 
> As TRACE.testGroup and TRACE_TraceObject.testGroup pass in those 
> failing/segmenting test runs I am not sure what the cause would be (in which 
> test the segmentation fault gets triggered). 
> 
> It is also interesting that the 32-bit Windows 11 test run works, but the 
> 64-bit Windows 11 test run has an exception. On Windows 10 it seems that 
> both, the 32- and the 64-bit version have a segmentation fault. But then, the 
> last successful run of the test suite is reported to have been more than 11 
> months ago on Windows 10 64-bit?
> 
> <fp9TWZOQs091SwSe.png>
> 
> ---rony
> 
> P.S.: Will look into this specific testGroup later on my Windows machine with 
> a debug version of 64-bit ooRexx. 
> 
> 
> 
> _______________________________________________
> 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