Apologies for the partial duplicate message, silly mail client on slow
internet connection...
On 22/05/2014 10:51, Dawid Loubser wrote:
Wow Peter, that sounds great! One would have to think one of the
target (niche) environments of River is that requiring some of these
other more interesting
See https://builds.apache.org/job/river-qa-refactor-j9/5/changes
Changes:
[peter_firmstone] RIVER-439 Removed dependencies on Sun JVM specific internal
implementation classes, enabling building on Java 1.6 IBM J9
--
[...truncated 7202 lines...]
Jini has a small but loyal user base in financial services.
Looks like River is building on J9, real time java and IIOP seems to be
working too.
I'm not expecting many tests to pass at this stage, since many
permissions will be different, at least it's all compilling now.
Cheers,
Peter.
[java] -
[java] GENERAL HARNESS CONFIGURATION INFORMATION:
[java]
[java]Date started:
[java] Thu May 22 11:23:39 UTC 2014
[java]Installation directory of the JSK:
[java]
This is all good, but I would personally be interested in getting to a
release based on the QA branch with less remaining development. I would
suggest rapid iterations for releases with incremental change until a QA
branch based release is stable.
On Thu, May 22, 2014 at 7:24 AM, Peter
The build will be ready for release when test failures are low, once we
reach that milestone, we can perform rapid iterative releases.
The recent fix to JERI appears to have increased stability, at least
locally, although this isn't showing through on Jenkins yet.
You could say I took some
See https://builds.apache.org/job/river-qa-refactor-solaris/62/changes
Changes:
[peter_firmstone] RIVER-439 Removed dependencies on Sun JVM specific internal
implementation classes, enabling building on Java 1.6 IBM J9
[peter_firmstone] RIVER-439 Removed dependencies on Sun JVM specific
Much-deserved easy tak, Peter!
I hope many others on this list share my quiet appreciation for the
massive work you are putting into the codebase.
Dawid
On 22/05/2014 14:08, Peter Firmstone wrote:
The build will be ready for release when test failures are low, once
we reach that milestone, we
Yes, very much. Bryan
On May 22, 2014, at 8:19 AM, Dawid Loubser da...@travellinck.com wrote:
Much-deserved easy tak, Peter!
I hope many others on this list share my quiet appreciation for the
massive work you are putting into the codebase.
Dawid
On 22/05/2014 14:08, Peter Firmstone
On 5/22/2014 5:08 AM, Peter Firmstone wrote:
...
You could say I took some time out, to do something easy, at least
compared to the hair pulling concurrency bugs and race conditions I've
been focused on.
...
When you are ready to return to the concurrency bugs and race
conditions, send me
Well the news is someone aborted the build, this is quite common with
River builds, I don't know whether it's because people think the build
is hung, because it goes for so long or they need to shutdown a node for
maintenance, who knows.
If people can perform test runs on their own hardware,
See https://builds.apache.org/job/river-qa-refactoring-jdk7/50/changes
Changes:
[peter_firmstone] RIVER-439 Removed dependencies on Sun JVM specific internal
implementation classes, enabling building on Java 1.6 IBM J9
[peter_firmstone] RIVER-439 Removed dependencies on Sun JVM specific
I've seen this test fail on Java 8 on Windows 32 bit and Java 7 on Linux
(Jenkins).
This test relates to ServiceDiscoveryManager.
The test doesn't fail consistently.
Running com/sun/jini/test/impl/servicediscovery/event/ReRegisterBadEquals.td
Time is Wed Feb 26 14:39:57 UTC 2014
Starting test
13 matches
Mail list logo
