On Sat, Apr 3, 2010 at 1:49 PM, CVBruce <[email protected]> wrote:
> Thanks for responding Rick,
>
> I added a TRACE I; to the failing test. Here is the output. I'd like
> to point out that this time I didn't get the error. Could this be
> because I added the TRACE statements? I need help to understand what
> the trace is trying to tell me.
>
> Thanks,
>
> Bruce
> [email protected] /Users/bjskelly/4.0.1> ./testOORexx.rex -X
> native_api
> ooTest.frm::routine::setExternalDir() line: 171
> Need code for operating system: MACOSX
> Searching for test containers...
> Executing automated test
> suite................ ..............................
> ....................
> 1879 *-* self~ensureEmptyQueue
> >V> SELF => "a TIME.long.testGroup"
> 1880 *-* currentTime = time()
> >F> TIME => "10:43:58"
> >>> "10:43:58"
> >=> CURRENTTIME <= "10:43:58"
> 1882 *-* cb1=TIME('r')||'*'||TIME('R')
> >L> "r"
> >A> "r"
> >F> TIME => "0"
> >L> "*"
> >O> "||" => "0*"
> >L> "R"
> >A> "R"
> >F> TIME => "0"
> >O> "||" => "0*0"
> >>> "0*0"
> >=> CB1 <= "0*0"
> 1883 *-* Call sysSLEEP '1'
> >L> "1"
> >A> "1"
> . >>> "0"
> 1884 *-* Call SCBTIMEB
> ........... 1885 *-* Call sysSLEEP '1'
> >L> "1"
> >A> "1"
> . >>> "0"
> 1886 *-* Pull cb5 cb6
> >>> "0*0 5.000757*5.000757"
> >=> CB5 <= "0*0"
> >=> CB6 <= "5.000757*5.000757"
> 1887 *-* Pull cb2 cb3
> >>> "0*0 5.000371*5.000371"
> >=> CB2 <= "0*0"
> >=> CB3 <= "5.000371*5.000371"
> 1888 *-* cb4=TIME('r')||'*'||TIME('R')
> >L> "r"
> >A> "r"
> >F> TIME => "13.007292"
> >L> "*"
> >O> "||" => "13.007292*"
> >L> "R"
> >A> "R"
> >F> TIME => "13.007292"
> >O> "||" => "13.007292*13.007292"
> >>> "13.007292*13.007292"
> >=> CB4 <= "13.007292*13.007292"
> 1889 *-* Parse Var cb1 cb1a '*' cb1b
> >V> CB1 => "0*0"
> >>> "0*0"
> >L> "*"
> >>> "*"
> >=> CB1A <= "0"
> >=> CB1B <= "0"
> 1890 *-* Parse Var cb2 cb2a '*' cb2b
> >V> CB2 => "0*0"
> >>> "0*0"
> >L> "*"
> >>> "*"
> >=> CB2A <= "0"
> >=> CB2B <= "0"
> 1891 *-* Parse Var cb3 cb3a '*' cb3b
> >V> CB3 => "5.000371*5.000371"
> >>> "5.000371*5.000371"
> >L> "*"
> >>> "*"
> >=> CB3A <= "5.000371"
> >=> CB3B <= "5.000371"
> 1892 *-* Parse Var cb4 cb4a '*' cb4b
> >V> CB4 => "13.007292*13.007292"
> >>> "13.007292*13.007292"
> >L> "*"
> >>> "*"
> >=> CB4A <= "13.007292"
> >=> CB4B <= "13.007292"
> 1893 *-* Parse Var cb5 cb5a '*' cb5b
> >V> CB5 => "0*0"
> >>> "0*0"
> >L> "*"
> >>> "*"
> >=> CB5A <= "0"
> >=> CB5B <= "0"
> 1894 *-* Parse Var cb6 cb6a '*' cb6b
> >V> CB6 => "5.000757*5.000757"
> >>> "5.000757*5.000757"
> >L> "*"
> >>> "*"
> >=> CB6A <= "5.000757"
> >=> CB6B <= "5.000757"
> 1897 *-* self~assertTrue(self~midnightDidNotHappen(currentTime),
> 'Midnight did not occur while this test case was running.')
> >V> SELF => "a TIME.long.testGroup"
> >V> SELF => "a TIME.long.testGroup"
> >V> CURRENTTIME => "10:43:58"
> >A> "10:43:58"
> >M> "MIDNIGHTDIDNOTHAPPEN" => "1"
> >A> "1"
> >L> "Midnight did not occur while this test case was running."
> >A> "Midnight did not occur while this test case was running."
> 1899 *-* self~assertSame(cb1a, cb1b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB1A => "0"
> >A> "0"
> >V> CB1B => "0"
> >A> "0"
> 1900 *-* self~assertSame(cb2a, cb2b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB2A => "0"
> >A> "0"
> >V> CB2B => "0"
> >A> "0"
> 1901 *-* self~assertSame(cb3a, cb3b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB3A => "5.000371"
> >A> "5.000371"
> >V> CB3B => "5.000371"
> >A> "5.000371"
> 1902 *-* self~assertSame(cb4a, cb4b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB4A => "13.007292"
> >A> "13.007292"
> >V> CB4B => "13.007292"
> >A> "13.007292"
> 1903 *-* self~assertSame(cb5a, cb5b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB5A => "0"
> >A> "0"
> >V> CB5B => "0"
> >A> "0"
> 1904 *-* self~assertSame(cb6a, cb6b)
> >V> SELF => "a TIME.long.testGroup"
> >V> CB6A => "5.000757"
> >A> "5.000757"
> >V> CB6B => "5.000757"
> >A> "5.000757"
> 1906 *-* self~assertSame(cb5a, '0')
> >V> SELF => "a TIME.long.testGroup"
> >V> CB5A => "0"
> >A> "0"
> >L> "0"
> >A> "0"
> 1907 *-* self~assertTrue(cb6a>='5')
> >V> SELF => "a TIME.long.testGroup"
> >V> CB6A => "5.000757"
> >L> "5"
> >O> ">=" => "1"
> >A> "1"
> 1908 *-* self~assertSame(cb2a, '0')
> >V> SELF => "a TIME.long.testGroup"
> >V> CB2A => "0"
> >A> "0"
> >L> "0"
> >A> "0"
The following line was the assertion that was failing originally. The
critical work here is done in the SCBTIMEB routine, which calls reset
on the elasped timer, sleeps for 5 seconds, and pushes a line with the
elapsed time. Assuming everything has worked correctly, then the
elapsed time must be at least 5 seconds. It is possible that syssleep
might be waking up at slightly under 5 seconds and the resolution of
the clock is such that time('r') is returning a value slightly less
than 5 seconds, resulting in the failure.
> 1909 *-* self~assertTrue(cb3a>='5')
> >V> SELF => "a TIME.long.testGroup"
> >V> CB3A => "5.000371"
> >L> "5"
> >O> ">=" => "1"
> >A> "1"
> 1910 *-* self~assertTrue(cb4a>='13')
> >V> SELF => "a TIME.long.testGroup"
> >V> CB4A => "13.007292"
> >L> "13"
> >O> ">=" => "1"
> >A> "1"
> 1911 *-* TRACE O;
> ..................................foo
> ........
> ..sh: zxyabc: command not found
> ..sh: zxyabc: command not found
> ......
>
> ooTest Framework - Automated Test of the ooRexx Interpreter
>
>
> Interpreter: REXX-ooRexx_4.0.1(MT) 6.03 1 Apr 2010
> Addressing Mode: 32
> ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
>
> Tests ran: 18284
> Assertions: 573379
> Failures: 1
> Errors: 0
> Skipped files: 33
>
> [failure] [20100403 10:44:41.141273]
> svn: r3371 Change date: 2008-09-20 21:33:29 -0700
> Test: TEST_VALUE
> Class: VALUE.testGroup
> File: /Users/bjskelly/4.0.1/ooRexx/base/bif/VALUE.testGroup
> Line: 346
> Failed: assertSame
> Expected: [[], identityHash="5457523"]
> Actual: [[7], identityHash="12617319"]
>
> File search: 00:00:01.693565
> Suite construction: 00:00:01.025990
> Test execution: 00:02:11.502115
> Total time: 00:02:14.960030
>
> On Apr 3, 2010, at 10:23 AM, Rick McGuire wrote:
>
>> I'm not too concerned about the value() failure. We're seeing the
>> same thing on AIX and have decided not to fix this for 4.0.1 because
>> the fix requires a rewrite of how that function works. The time()
>> failure would require some tracing to see what's really going wrong,
>> but my first guess is the syssleep() function isn't working correctly.
>>
>> Rick
>>
>> On Sat, Apr 3, 2010 at 12:55 PM, CVBruce <[email protected]> wrote:
>>> Hi,
>>> I ran the testOORexx.rex script. Here is the output. I need help
>>> on what
>>> to do next.
>>> I do have a Mac OS X installer ready to go. What should I do with
>>> it.
>>> Yours,
>>> Bruce
>>> ooTest Framework - Automated Test of the ooRexx Interpreter
>>>
>>> Interpreter: REXX-ooRexx_4.0.1(MT) 6.03 1 Apr 2010
>>> Addressing Mode: 32
>>> ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
>>> Tests ran: 18284
>>> Assertions: 573378
>>> Failures: 2
>>> Errors: 0
>>> Skipped files: 33
>>> [failure] [20100401 21:34:08.425976]
>>> svn: r4227 Change date: 2009-02-26 10:38:21 -0800
>>> Test: TEST_5
>>> Class: TIME.long.testGroup
>>> File: /Users/bjskelly/4.0.1/ooRexx/base/bif/TIME.testGroup
>>> Line: 1908
>>> Failed: assertTrue
>>> Expected: [1]
>>> Actual: [[0], identityHash="786542"]
>>> [failure] [20100401 21:34:38.474249]
>>> svn: r3371 Change date: 2008-09-20 21:33:29 -0700
>>> Test: TEST_VALUE
>>> Class: VALUE.testGroup
>>> File: /Users/bjskelly/4.0.1/ooRexx/base/bif/VALUE.testGroup
>>> Line: 346
>>> Failed: assertSame
>>> Expected: [[], identityHash="4441663"]
>>> Actual: [[7], identityHash="18479832"]
>>> File search: 00:00:01.539506
>>> Suite construction: 00:00:01.165404
>>> Test execution: 00:02:26.241587
>>> Total time: 00:02:29.553706
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Oorexx-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
