After discussing with Michael Durig created OAK-943 [1] and provided a
patch to improve the message.
[1] https://issues.apache.org/jira/browse/OAK-943
Chetan Mehrotra
On Thu, Aug 1, 2013 at 7:28 PM, Chetan Mehrotra
chetan.mehro...@gmail.com wrote:
In one of the test scenario I am getting
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/2974
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
sorry... my bad. i will fix it right away.
On 8/7/13 9:36 AM, build...@apache.org build...@apache.org wrote:
The Buildbot has detected a new failure on builder oak-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/2974
Buildbot
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/2977
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
Hi,
While trying to debug Oak related logic in multi threaded environment
it would be helpful if we can have some way to uniquely refer to any
session instance. Just like the sessionName [1] in JR2. One way would
be to assign a unique sessionName to ContentSession and that name
would be used in
On 7.8.13 15:19, Chetan Mehrotra wrote:
some way to uniquely refer to any
session instance
Agreed, this would be helpful. We might also think of exposing this (and
other useful but non security relevant information) through toString().
Michael
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/2984
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
the reason phrase is a bit misleading. the build failed because
it was still using an old jackrabbit-jcr-tests snapshot version.
should be fine once the fix for JCR-3639 makes its way to
the build machine.
regards
marcel
-Original Message-
From: build...@apache.org
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/2990
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
