Hello Mike,
> Most people on Windows call an abend, a crash.
Oh, crash. Makes sense. Still, though, abend makes sense to me, but I can
include crash as part of my vocabulary. ;-)
> Add the -s flag to your command line and run
> the test suite until it crashes.
Thank you for the information. While writing this reply, I ran the test
with the "-s" option and it crashed / terminated / abended at:
Executing tests from C:\Program Files\...\base\class\RexxContext.testGroup
I'm including (inline) the generated output. (Please let me know if
appending (not attaching, but appending) output, in the future, would be
better or it doesn't matter to you.)
(BTW, feel free to tell / have me direction this conversation to another
mailing list or email.)
---------- Start of the latest run (with -s this time) output ----------
Thu 02/13/2014 12:44:48.79 C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06>testOORexx.rex -X native_api -s
Searching for test containers......
Executing automated test suite
Executing tests from C:\Program Files\...\ooRexx\SimpleTests.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\Assignments.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\ShortCircuitAnd.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\ABBREV.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\ABS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\ADDRESS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\ARG.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\B2X.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\BEEP.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\BITAND.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\BITOR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\BITXOR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\C2D.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\C2X.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\CENTER.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\CENTRE.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\CHANGESTR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\CHARIN.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\CHAROUT.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\CHARS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\COMPARE.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\CONDITION.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\COPIES.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\COUNTSTR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\D2C.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\D2X.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\DATATYPE.testGroup
000000000C 000000000C
000000000C 000000000C
Executing tests from C:\Program Files\...\ooRexx\base\bif\DATE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\DELSTR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\DELWORD.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\DIGITS.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\ERRORTEXT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\FILESPEC.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\FORM.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\FORMAT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\FUZZ.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\INSERT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LASTPOS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LEFT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LENGTH.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LINEIN.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LINEOUT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LINES.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\LOWER.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\MAX.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\MIN.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\OVERLAY.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\POS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\QUALIFY.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\QUEUED.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\RANDOM.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\REVERSE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\RIGHT.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\SIGN.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\SOURCELINE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\SPACE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\STREAM.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\STREAM.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\STRIP.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\SUBSTR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\SUBWORD.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\SYMBOL.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\TIME.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\TIME.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\TRANSLATE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\TRUNC.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\UPPER.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\VALUE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\VAR.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\VERIFY.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\WORD.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\WORDINDEX.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\bif\WORDLENGTH.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\WORDPOS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\WORDS.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\X2B.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\X2C.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\X2D.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\bif\XRANGE.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Array.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Bag.testGroup
Executing tests from C:\Program Files\...\base\class\CircularQueue.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Class.testGroup
Executing tests from C:\Program Files\...\CollectionSetlikeMethods.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Comparator.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\DateTime.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Directory.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\File.testGroup
Executing tests from C:\Program Files\...\base\class\IdentityTable.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\List.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Method.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Monitor.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Object.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Orderable.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Package.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Properties.testGroup
Executing tests from C:\Program Files\...\ooRexx\base\class\Queue.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\QueueRGF.testGroup
Executing tests from C:\Program
Files\...\ooRexx\base\class\Relation.testGroup
Executing tests from C:\Program Files\...\base\class\RexxContext.testGroup
Thu 02/13/2014 12:47:26.56 C:\Program Files\ooRexx\ooTest-4.2.0-snapshot06>
---------- End of the latest run (with -s this time) output ----------
OK, so from your instructions I determined the failing test to be:
base\class\RexxContext.testGroup
But, given everything else has ooRexx at the start, I decided to add
ooRexx\ to the line. (FYI: Later on I tried a run as it appears and, of
course, it failed not being able to find the test container. *QUESTION /
THOUGH:* *I wonder why the "-s" run failed to include the ooRexx\ in the
output line?* Is there a limit on the output line and thus lines become
reduced in size?
In any case, to the above question, I ran the specific test individually
and it crashed / abended, just as it did in the full run.
---------- Start of running just the test that failed above ----------
Thu 02/13/2014 13:00:41.37 C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06>testOORexx.rex -X native_api -f
ooRexx\base\class\RexxCon
text.testGroup
Searching for test containers..
Executing automated test suite
Thu 02/13/2014 13:03:24.12 C:\Program Files\ooRexx\ooTest-4.2.0-snapshot06>
---------- End of running just the test that failed above ----------
> If it does crash, then good, maybe we can track it down.
> Run just the test group again with the -S flag. This will
> print out the test cases as they are executed:
OK, running it again with the "-s" flag (option) this time around.
---------- Start of running just the test that failed above and using the
"-s" option ----------
Thu 02/13/2014 13:28:12.62 C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06>testOORexx.rex -X native_api -s -f
ooRexx\base\class\Rexx
Context.testGroup
Searching for test containers..
Executing automated test suite
Executing tests from C:\Program Files\...\base\class\RexxContext.testGroup
Thu 02/13/2014 13:29:05.98 C:\Program Files\ooRexx\ooTest-4.2.0-snapshot06>
---------- End of running just the test that failed above and using the
"-s" option ----------
BTW, Something I noticed between our two test runs that is different. It
may or may not point to the problem (or it might be a red herring).
NOTE: This line (see below) ONLY comes up with a run completes. When
ooRexx crashes / abends the line doesn't come up and thus till I happen to
perform a run that completed (it was the one where the test wasn't found),
I never saw the difference between these two (see below) lines.
Line from your example: Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04
30 Jan 2014
Line from my run: Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit
6.04 19 Jan 2014
The difference is the date (19 Jan 2014 versus 30 Jan 2014). The Rexx
version, though, are the same and the test doesn't say I'm running the
wrong level test, etc. Maybe the date doesn't matter.
*SUGGESTION: * As the test containers can cause a crash / abend, maybe
printing out at the start important information that will change (e.g. such
as software levels) at the beginning of the run. Then again maybe what I'm
reporting above is NOT important and therefor this suggestion is moot.
> If you can report that information back to us, we'd appreciate it.
Yes, of course, it is the least I can do (when I can do it) given all the
work you're doing developing, maintaining, and supporting ooRexx.
> Thanks for running the test suite to being with.
Ah, you're welcome, but I'm not sure what you're trying to say here. In
any case, though, You're Welcome Very Much! :-)
*THOUGHT / SUGGESTION:*
Up front, let me first say a couple of things:
1. I could be seeing a problem that isn't important or isn't really
there. If this is the case, sorry for bothering you.
2. Given so many people (these days) are into computer and with so wide
of backgrounds, I find it difficult (sometimes) to tell the wheat from the
chaff. I like to think of myself as part of the wheat, given I've been
programming, designing, testing, documenting both programs and operating
systems since 1974.
OK, with that out of the way.
The problem I think exists is getting enough people to test and report
ooRexx candidates on a regular basis. If I'm wrong, well, the rest of this
doesn't really matter.
My thought isn't really new. It comes from the various distributed
computing projects, such as GIMPS, FreeHAL, the many @home projects, etc.
Why not provide a way by which people can distribute the testing and
reporting of the ooRexx test suit? The person providing the environment
would install ooRexx and the distribution test software.
When D-Test notices a new candidate is available, it would let the user
know and *IF/ONLY IF* the user upgraded to the candidate would it run the
test suite and report back. Of course conditions (such as mine with the
crash / abend) or tests requiring human intervention would present some
challenges, but I suspect it's doable.
The D-Test package could even check the results and as did in this email
run a specific test. Should D-Test need an human to help it, well, it
could always ask, right?
Anyway, my thought is people might be more willing to test and report using
a distributed method than a "manual" method. Plus given how automated the
test suite is at this time (GREAT job, BTW) creating D-Test should be
relatively straight forward and possible.
SIDE benefit *might *be when a person has a problem with ooRexx a developer
or support person could use D-Test to get a better handle on the person's
computer, environment, and the issue at hand.
YEAH, I know you're already busy and it isn't like this is a paying gig! I
fully understand. ;-)
Take care and I look forward both to hearing from you and helping Rexx
improve,
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
