Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Moritz Hoffmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/30/2014 01:55 PM, Rick McGuire wrote: > And that's one of the failures I just fixed. I can confirm that, thank you! :-) Moritz - -- Moritz Hoffmann http://antiguru.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuP

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Rick McGuire
Yep, should be good to go, other than the mystery of the MutableBuffer failures. Rick On Thu, Jan 30, 2014 at 1:53 PM, Mark Miesfeld wrote: > On Thu, Jan 30, 2014 at 8:25 AM, David Ashley wrote: > >> I usually take one of the overnight builds and make them release >> candidates. So just say "g

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Mark Miesfeld
On Thu, Jan 30, 2014 at 8:25 AM, David Ashley wrote: > I usually take one of the overnight builds and make them release > candidates. So just say "go" and I can be ready the next day. > Go. After tonight's build. I think Rick is done. -- Mark Miesfeld > -

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread David Ashley
I usually take one of the overnight builds and make them release candidates. So just say "go" and I can be ready the next day. David Ashley On Thu, 2014-01-30 at 06:33 -0800, Mark Miesfeld wrote: > > On Thu, Jan 30, 2014 at 4:16 AM, Rick McGuire > wrote: > > Ok, that didn't take as lo

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Mark Miesfeld
On Thu, Jan 30, 2014 at 4:16 AM, Rick McGuire wrote: > Ok, that didn't take as long as I expected. I'm now getting a clean run > of the entire suite except for one of the Windows event viewer tests that's > always been a bit flaky. We definitely need to spin new release > candidates. > I have

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Rick McGuire
Ok, that didn't take as long as I expected. I'm now getting a clean run of the entire suite except for one of the Windows event viewer tests that's always been a bit flaky. We definitely need to spin new release candidates. Rick On Thu, Jan 30, 2014 at 6:45 AM, Rick McGuire wrote: > I did a

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Rick McGuire
I did a complete run of the test suite, and found a few more errors that I probably won't be able to resolve until later today. It's a little strange that your run didn't show these or the crash that Moritz and I encountered. Are you sure you're running the latest version of the tests? Rick On

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Rick McGuire
And that's one of the failures I just fixed. Rick On Thu, Jan 30, 2014 at 5:06 AM, Moritz Hoffmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 01/30/2014 11:04 AM, Moritz Hoffmann wrote: > > Tests also failing on Debian, oorexx 4.2.0 branch and trunk test > > suite. I can

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Moritz Hoffmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/30/2014 11:04 AM, Moritz Hoffmann wrote: > Tests also failing on Debian, oorexx 4.2.0 branch and trunk test > suite. I can offer to give more info, but today I have a 6h exam > ;-) The offending test case is ... running TestCase object [testC

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Rick McGuire
The Class and Queue failures were problems in the test suite (they were never updated for the removal of serializable). I also found a crash in the RexxContext tests that was a bug, which I think justifies having another full release candidate. I'm not seeing any errors in the space tests, which

Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0

2014-01-30 Thread Moritz Hoffmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/30/2014 02:33 AM, David Ashley wrote: > There are some failures when I run the test suite against the > latest 4.20. build on Fedora 20 x86_64. Below is the output of the > report. > > I just want to make sure these are normal, but I believe t