CMIIW, but didn't Thomas "fix" this recently?
Michael
On 9.11.15 9:02 , Marcel Reutegger wrote:
this also happened on other branches every now and then. Does anyone
have a clue why this test is not stable?
-1 means the size is unknown, which is a valid return value according
to the JCR spec. Should we change the test to accept this value?
Regards
Marcel
On 05/11/15 17:17, "Alex Parvulescu" wrote:
build broke on oak-lucene with:
Failed tests:
testGetSize(org.apache.jackrabbit.core.query.QueryResultTest): Wrong size
of NodeIterator in result expected:<55> but was:<-1>
doesn't look related to my changes
On Thu, Nov 5, 2015 at 5:12 PM, Travis CI <ju...@apache.org> wrote:
Build Update for apache/jackrabbit-oak
-------------------------------------
Build: #6769
Status: Broken
Duration: 1451 seconds
Commit: da0de0f470c1be0a5e1ff1ddfad19bd097c72bd7 (1.2)
Author: Alexandru Parvulescu
Message: OAK-3587 SegmentNodeStore stricter checkpoint creation policy
- merged r1712730
git-svn-id:
https://svn.apache.org/repos/asf/jackrabbit/oak/branches/1.2@1712788
13f79535-47bb-0310-9956-ffa450edef68
View the changeset:
https://github.com/apache/jackrabbit-oak/compare/31e37f51f831...da0de0f47
0c1
View the full build log and details:
https://travis-ci.org/apache/jackrabbit-oak/builds/89463868
--
sent by Jukka's Travis notification gateway
