Hi all,
we have discussed this before. Thanks to Niall, all the JavaDoc issues are
now resolved, so I'm hoping to find the time this weekend to roll out an
RC.
There is one issue that we could consider for inclusion: LANG-990 - Avoid
String allocation in StrBuilder.append(CharSequence) [1]. This
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28605&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Apr 2014 04:21:10 +
Finished at: Thu 3 Apr 2014 04:24:33 +
Total time: 3m 23s
Build Trigger: Schedu
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28600&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Apr 2014 02:21:03 +
Finished at: Thu 3 Apr 2014 02:24:15 +
Total time: 3m 12s
Build Trigger: Schedu
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28597&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Apr 2014 01:21:09 +
Finished at: Thu 3 Apr 2014 01:24:28 +
Total time: 3m 19s
Build Trigger: Schedu
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28594&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 3 Apr 2014 00:23:35 +
Finished at: Thu 3 Apr 2014 00:26:56 +
Total time: 3m 21s
Build Trigger: Schedu
On 4/2/14, 3:38 PM, Gary Gregory wrote:
> Are the concurrency updates in Java 7 (or 8) of any help here?
The machinery is there in the 1.6 vintage classes we now use. We
just need to make fairness of the lock used by our
LinkedBlockingDeque configurable.
Phil
>
> Gary
>
>
> On Wed, Apr 2, 2014 a
Are the concurrency updates in Java 7 (or 8) of any help here?
Gary
On Wed, Apr 2, 2014 at 5:58 PM, Phil Steitz wrote:
> It looks to me like v 2 pools are no longer fair in the sense of
> 1.5.x (modulo lucky threads getting to wait on creates). I agree
> that the default should be no fairness
It looks to me like v 2 pools are no longer fair in the sense of
1.5.x (modulo lucky threads getting to wait on creates). I agree
that the default should be no fairness constraint, but it might be
good to make this configurable. This looks doable with another
small tweak to LinkedBlockingDeque.
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28574&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 2 Apr 2014 16:21:11 +
Finished at: Wed 2 Apr 2014 16:24:32 +
Total time: 3m 20s
Build Trigger: Schedu
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28571&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 2 Apr 2014 15:27:46 +
Finished at: Wed 2 Apr 2014 15:31:08 +
Total time: 3m 22s
Build Trigger: Forced
After your latest changes the output looks much better now.
java version "1.7.0_51"
OpenJDK Runtime Environment (IcedTea 2.4.4) (suse-24.13.5-x86_64)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)
Results :
Tests run: 396, Failures: 0, Errors: 0, Skipped: 0
[INFO] -
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28565&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 2 Apr 2014 13:21:07 +
Finished at: Wed 2 Apr 2014 13:24:22 +
Total time: 3m 14s
Build Trigger: Schedu
Am 02.04.2014 08:41, schrieb Thomas Vandahl:
On 31.03.14 23:56, sebb wrote:
The Continuum build reports lots of test failures.
For example:
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28476&projectId=286
The tests are very "noisy" when run interactively.
This makes it
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28560&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 2 Apr 2014 11:21:06 +
Finished at: Wed 2 Apr 2014 11:24:27 +
Total time: 3m 21s
Build Trigger: Schedu
On 02.04.14 12:23, sebb wrote:
> However I assume the tests are still "noisy" on MacOS.
> Once the unnecessary output is removed, can look at adding temporary
> additional debug for the failing test cases in Continuum.
Yes, I directed logging to a log file and removed some of the chatter.
We'll se
On 02.04.14 12:13, sebb wrote:
> On 2 April 2014 07:42, Thomas Vandahl wrote:
>> On 01.04.14 00:06, sebb wrote:
>>> Just been looking at the dependencies.
>>> Some of these are obsolete, for example commons-httpclient 3.0.1
>>
>> What do you mean by "obsolete"?
>
> No longer supported.
>
>> Use
Send from my mobile device
> Am 02.04.2014 um 12:19 schrieb sebb :
>
>> On 2 April 2014 07:49, Thomas Vandahl wrote:
>>> On 01.04.14 00:25, sebb wrote:
>>> Also, there is a source tree called auxiliary-builds/jdk14.
>>> Since the code now targets 1.6, I assume this is no longer needed?
>>
>>
On 2 April 2014 07:41, Thomas Vandahl wrote:
> On 31.03.14 23:56, sebb wrote:
>> The Continuum build reports lots of test failures.
>>
>> For example:
>>
>> https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28476&projectId=286
>>
>> The tests are very "noisy" when run interactiv
On 2 April 2014 07:49, Thomas Vandahl wrote:
> On 01.04.14 00:25, sebb wrote:
>> Also, there is a source tree called auxiliary-builds/jdk14.
>> Since the code now targets 1.6, I assume this is no longer needed?
>
> No. The source tree contains features (such as the JGroups cache) that
> have not m
On 2 April 2014 07:42, Thomas Vandahl wrote:
> On 01.04.14 00:06, sebb wrote:
>> Just been looking at the dependencies.
>> Some of these are obsolete, for example commons-httpclient 3.0.1
>
> What do you mean by "obsolete"?
No longer supported.
> Use 4.x? Or remove the dependency
> completely?
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28555&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 2 Apr 2014 09:21:02 +
Finished at: Wed 2 Apr 2014 09:24:24 +
Total time: 3m 22s
Build Trigger: Schedu
21 matches
Mail list logo
