Bertram,
I can't give you a lot of help right now, I will also send a post this
evening.
The basic idea is to determine which test group caused the crash, and maybe
which test in the test group.
To do this you use the optional flags to enable more verbose output. I
don't have access to a system with the test suite on it right now to give
you the exact flags, you'll need to figure them out yourself.
do testOORexx --help
and look for the option that prints out the test group names. Rerun the
test suite using that option and the last test group printed out at the
crash is probably the one that caused the crash.
Then run just that single test group using the -f option and see if it
still crashes when run by itself. If so, run just that test group using
the additional flag that prints out the test cases as they are executed.
If you narrow it done to an exact test case that causes the crash, then let
us know.
I have to say, I ran the snapshot test suite about 20 times over the
weekend and never saw a problem.
--
Mark Miesfeld
On Wed, Feb 12, 2014 at 1:50 PM, Bertram Moshier
<[email protected]>wrote:
> Hello,
>
> I just upgraded from 4.1.3 to 4.2.0 64-bit version.
>
> I'm on Windows 7 Ultimate x64 and this is my first time running the test
> suit, so please bear with me if I don't include what is necessary. My hope
> is to open a line of communications to the person(s) who need to know.
>
> I ran this test twice with the same result.
>
> While running the test I got the follow pop-up from Windows saying:
>
> -------------- Start of Dialog --------------
> Open Object Rexx Interface has stopped
> working
>
> A problem cause the program to stop working correctly.
> Windows will close the program and notify you if a solution is
> available.
>
> Close program button
> -------------- End of Dialog --------------
>
> The following is what I'm seeing when running the 4.2.0 test suit. Please
> note I'm including the date, time, path, and command line, in the first
> line.
>
> -------------- Start Command Output --------------
>
> Wed 02/12/2014 15:18:11.75 C:\Program
> Files\ooRexx\ooTest-4.2.0-snapshot06>testOORexx -X native_api
> Searching for test containers.....
> Executing automated test suite............. .000000000C 000000000C
> 000000000C 000000000C
> ................................
> ..................................................................
>
>
> -------------- End Command Output --------------
>
> OK, that's what I have to this point in time. I'm sure the "Abend Dialog
> Box," well that is what I call it, as when I was learning programming
> (VM/370, VS1, VS2, and DOS/VSE) we called abnormal termination of a program
> an abend.
>
> Questions:
>
> 1) BTW, can anyone tell me what does the Windows world call an abnormal
> termination of a program?
> 2) How should I proceed?
>
> Thank you,
>
> Bertram Moshier
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience. Start now.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Oorexx-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-users
>
>
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
