Hello,
I think that I have found the problem:
The run is OK:
==
# ./runTest.sh -X64 -f CHAROUT.testGroup
Setting env for AIX
User requested a 64 bit test suite run.
Searching for test containers..
Executing automated test suite. ...
ooTest Framework - Automate
Hello Mark,
Mark Miesfeld wrote:
> There is only one error here, as you mostly have come to realize I think.
>
> On Mon, May 18, 2009 at 12:44 AM, Rainer Tammer wrote:
>
>
>> [failure] [20090518 09:20:46.995363]
>> svn:r4672 Change date: 2009-05-14 19:04:09 +0200
>> Test: TEST_QUERYD
Rainer,
On Mon, May 18, 2009 at 5:00 AM, Rainer Tammer wrote:
> I did run the test suit under root (I know, you should not do this ...
> but ...:-) )
I always am root also. What I do is just run the test suite
completely, and expect to get that 1 failure. Then I just run the
Stream.testGroup
Rick McGuire wrote:
> I just took a quick look at these tests. The first failure might be
> caused by a directory left behind by an earlier test run, or a problem
> with the rexxutil SysFileExists() function.
>
>
OK,
I found the left over directory.
... test suit running ... result: The error i
I just took a quick look at these tests. The first failure might be
caused by a directory left behind by an earlier test run, or a problem
with the rexxutil SysFileExists() function.
The second failure will need some debugging to figure out why this
doesn't throw an error. This stream should be
Well, now it's down to the debugging. It looks like there are some
subtle differences in AIX vs. Linus behavior here. We can help you
locate the code involved, but you'll need to be the one to debug
what's going on.
Rick
On Mon, May 18, 2009 at 2:38 AM, Rainer Tammer wrote:
> Hallo,
> the new
Hallo,
this is the test result for 4702 / AIX 64 bit:
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 18 May 2009
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0
Tests ran: 18930
Assertions: 5756
Hallo,
the new SVN 4702 does no longer hang (AIX 5.3 / 32 bit). But it produces
3 errors:
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 18 May 2009
Addressing Mode: 32
ooRexxUnit: 2.0.0_3.2.0ooTest: 1.0.0_4.0.0
Tests ran:
Hello,
Mark Miesfeld wrote:
> On Sun, May 17, 2009 at 7:56 AM, Rainer Tammer wrote:
>
>
>> Rick McGuire wrote:
>>
>>> Make sure that you've got the correct version of rxapi running.
>>>
>> I kill the rxapi 3 times, cleaned the shared memory and reinstalled rexx
>> ... no luck.
>>
Hello Mark,
Mark Miesfeld wrote:
> On Sun, May 17, 2009 at 4:20 AM, Rick McGuire wrote:
>
>
>> Make sure that you've got the correct version of rxapi running. There
>> was also one change to the APIs, so make sure you've rebuilt all of
>> the programs used for the external tests.
>>
>
>
On Sun, May 17, 2009 at 7:56 AM, Rainer Tammer wrote:
> Rick McGuire wrote:
>> Make sure that you've got the correct version of rxapi running.
> I kill the rxapi 3 times, cleaned the shared memory and reinstalled rexx
> ... no luck.
Rainer,
If I had something like this on a Linux box, I would:
On Sun, May 17, 2009 at 4:20 AM, Rick McGuire wrote:
> Make sure that you've got the correct version of rxapi running. There
> was also one change to the APIs, so make sure you've rebuilt all of
> the programs used for the external tests.
Rainer,
If you use the -B option it forces all the exte
Hello,
Rick McGuire wrote:
> Make sure that you've got the correct version of rxapi running.
I kill the rxapi 3 times, cleaned the shared memory and reinstalled rexx
... no luck.
The standard samples are working
> There
> was also one change to the APIs, so make sure you've rebuilt all of
>
Make sure that you've got the correct version of rxapi running. There
was also one change to the APIs, so make sure you've rebuilt all of
the programs used for the external tests.
Rick
On Sun, May 17, 2009 at 5:07 AM, Rainer Tammer wrote:
> Hello,
> I just have rebuild the beta. Unfortunately t
Hello,
I just have rebuild the beta. Unfortunately the testsuite hangs...
AIX / 32 bit build / SVN 4688:
60 *-* expose called
42 *-* trap = .PullTrap~new
REX0048E: Error 48 running
/daten/source/ooRexx/test/trunk/ooRexx/API/oo/tests/traceExit.rex line
60: Failure in syste
REX0425E: Error
Hello,
Mark Miesfeld wrote:
> On Wed, May 13, 2009 at 11:30 PM, Rainer Tammer wrote:
>
>
>> OK, I will rebuild the AIX binaries...
>>
>
> Rainer, I'm going to hold of and just do a new build on Sunday and
> announce it Sunday evening.
>
> If / when you have time, it would be nice if you c
On Wed, May 13, 2009 at 11:30 PM, Rainer Tammer wrote:
> OK, I will rebuild the AIX binaries...
Rainer, I'm going to hold of and just do a new build on Sunday and
announce it Sunday evening.
If / when you have time, it would be nice if you could do a personal
build and run the test suite. I've
On Wed, May 13, 2009 at 7:53 AM, Rick McGuire wrote:
> Sunday is tutorials only. Gil gives his presentation about the new
> features Monday morning, so I think a Sunday build would be great.
Turns out I ran into a few snags yesterday and haven't resolved them
all yet. Rather than announce a ne
Hello,
OK, I will rebuild the AIX binaries...
Bye
Rainer
Rick McGuire wrote:
> We should also think about doing a beta refresh this weekend so a
> fresh version is available during the Symposium.
>
> Rick
>
> On Wed, May 13, 2009 at 10:30 AM, Mark Miesfeld wrote:
>
>> Wanted to let people k
Wish you guys could be here too.
Anyway, thanks for all the hard work you have put in.
Jon
2009/5/13 Rick McGuire
> Sunday is tutorials only. Gil gives his presentation about the new
> features Monday morning, so I think a Sunday build would be great.
>
> Rick
>
> On Wed, May 13, 2009 at 10:5
Sunday is tutorials only. Gil gives his presentation about the new
features Monday morning, so I think a Sunday build would be great.
Rick
On Wed, May 13, 2009 at 10:52 AM, Mark Miesfeld wrote:
> On Wed, May 13, 2009 at 7:45 AM, Rick McGuire wrote:
>
>> We should also think about doing a beta
On Wed, May 13, 2009 at 7:45 AM, Rick McGuire wrote:
> We should also think about doing a beta refresh this weekend so a
> fresh version is available during the Symposium.
Okay, I'll do one Saturday afternoon and get it available on
SourceForge. Or, ... I forget, do they start arriving on Sunda
Mark Miesfeld wrote:
> Wanted to let people know:
>
> * I will be out of touch May 24th through June 7th, with no Internet access.
>
> * I'm planning on rebuilding the beta release today and making it available.
>
> Not sure how that effects the release plans. I know we were shooting
> for the end
On Wed, May 13, 2009 at 7:33 AM, Rick McGuire wrote:
> That seems like a reasonable plan.
Good.
>> Release Candidate. Then do the final release around May 8th, provided
I meant June 8th of course.
--
Mark Miesfeld
-
We should also think about doing a beta refresh this weekend so a
fresh version is available during the Symposium.
Rick
On Wed, May 13, 2009 at 10:30 AM, Mark Miesfeld wrote:
> Wanted to let people know:
>
> * I will be out of touch May 24th through June 7th, with no Internet access.
>
> * I'm p
That seems like a reasonable plan.
Rick
On Wed, May 13, 2009 at 10:30 AM, Mark Miesfeld wrote:
> Wanted to let people know:
>
> * I will be out of touch May 24th through June 7th, with no Internet access.
>
> * I'm planning on rebuilding the beta release today and making it available.
>
> Not su
Wanted to let people know:
* I will be out of touch May 24th through June 7th, with no Internet access.
* I'm planning on rebuilding the beta release today and making it available.
Not sure how that effects the release plans. I know we were shooting
for the end of May. It seems the rate of 'sh
27 matches
Mail list logo
