Build failed in Jenkins: river-qa-refactor-jdk7 #54

2013-04-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/river-qa-refactor-jdk7/54/changes Changes: [peter_firmstone] Changes to mahalo for safe publication, added Starter to TxnManagerImpl and improved atomicity, fields made final and volatile all tests passing on sparc. Changes to CombinerSecurityManager and

Re: Next steps after 2.2.1 release

2013-04-07 Thread Peter Firmstone
Greg, You need to spend some more time figuring out why those tests are failing, that isn't normal, when 280 tests fail, there's usually something wrong with configuration. The qa test suite just isn't that brittle ;) The tests that fail due to concurrency errors don't fail often, we're

Re: Next steps after 2.2.1 release

2013-04-07 Thread Dan Creswell
On 7 April 2013 05:24, Patricia Shanahan p...@acm.org wrote: On 4/6/2013 7:26 PM, Greg Trasuk wrote: ... Once we have a stable set of regression tests, then OK, we could think about improving performance or using Maven repositories as the codebase server. ... I think there is something

Re: QA harness output - where is it?

2013-04-07 Thread Dan Creswell
Before running, you'll also need to edit build.properties and tweak river.home and log.config... On 6 April 2013 01:04, Peter Firmstone j...@zeus.net.au wrote: Greg, Copy the attached logging.properties file to your home directory. Copy the build.properties file to your trunk directory.

Re: Next steps after 2.2.1 release

2013-04-07 Thread Dan Creswell
True, for a definition of micro-benchmark you have decided for yourself rather than asked me to clarify On 7 April 2013 09:37, Patricia Shanahan p...@acm.org wrote: On 4/7/2013 1:04 AM, Dan Creswell wrote: On 7 April 2013 05:24, Patricia Shanahan p...@acm.org wrote: On 4/6/2013 7:26

Re: Next Release

2013-04-07 Thread Peter Firmstone
The situation would still have occurred, the release process was delayed by synchronization bugs, without which the release would have been much simpler with fewer changes. Of course the code is actually much better now, so it's not a bad situation, we just need to make sure testing is very

Re: jtsk/branches/2.2

2013-04-07 Thread Greg Trasuk
On Sun, 2013-04-07 at 02:53, Peter Firmstone wrote: Just a quick note, please don't modify 2.2 directly, it's a frozen snapshot of our last release. Please make an svn copy 2.2.1 We have policy on this. From http://river.apache.org/development-process.html Once a release candidate is

Re: Next steps after 2.2.1 release

2013-04-07 Thread Greg Trasuk
On Sun, 2013-04-07 at 06:34, Peter Firmstone wrote: Oh, hang on, are you developing on Windows? If so, it's not supported in 2.2.0. OSX 10.8 in this case, although I also plan to run the test suite on Windows XP32 and Win7-64. Possibly also Solaris 10. As I recall the Windows not

Re: Next steps after 2.2.1 release

2013-04-07 Thread Dan Creswell
On 7 April 2013 15:18, Dennis Reedy dennis.re...@gmail.com wrote: On Apr 6, 2013, at 1026PM, Greg Trasuk wrote: Proposal 1 - Release version 2.2.1 from the 2.2 branch. +1 for this, we really need to get this done, and get this done before the end of the month. 2 -

Next steps after 2.2.1 release

2013-04-07 Thread Greg Trasuk
OK, so in my last message I talked about how (speaking only for myself) I'm a little nervous about the state of the trunk. So what now? Problems we need to avoid in this discussion: - - Conflation of source tree structure issues

Re: Next steps after 2.2.1 release

2013-04-07 Thread Greg Trasuk
On Sun, 2013-04-07 at 10:18, Dennis Reedy wrote: On Apr 6, 2013, at 1026PM, Greg Trasuk wrote: Proposal 1 - Release version 2.2.1 from the 2.2 branch. +1 for this, we really need to get this done, and get this done before the end of the month. Agreed. I was

Re: Next steps after 2.2.1 release

2013-04-07 Thread Peter
Greg, why have you repeated this message? I think this is a deliberate attack on the project because you haven't been following development in trunk and now you're scared because you see changes you don't understand. I've been following your developments in surrogates, an impressive amount of

Jenkins build is back to normal : river-qa-refactoring #65

2013-04-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/river-qa-refactoring/65/changes

Re: Next steps after 2.2.1 release

2013-04-07 Thread Greg Trasuk
On Sun, 2013-04-07 at 17:54, Peter wrote: Greg, why have you repeated this message? First time I sent it was from the wrong email address, so it got hung up in moderation. I sent it again from my subscribed address. I'm guessing someone just moderated the original through. Anyway, let's

Re: Next steps after 2.2.1 release

2013-04-07 Thread Patricia Shanahan
On 4/7/2013 5:03 PM, Greg Trasuk wrote: ... I'm honestly and truly not passing judgement on the quality of the code. I honestly don't know if it's good or bad. I have to confess that, given that Jini was written as a top-level project at Sun, sponsored by Bill Joy, when Sun was at the top of

Build failed in Jenkins: river-qa-refactor-jdk7 #55

2013-04-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/river-qa-refactor-jdk7/55/ -- [...truncated 7613 lines...] [java] Warning: Nested class URLClassLoader$3 has different preferred state than outer class URLClassLoader [java] Warning: Nested class