[jira] [Commented] (OAK-156) Observation events need Session.refresh

[ https://issues.apache.org/jira/browse/OAK-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410521#comment-13410521 ] Jukka Zitting commented on OAK-156: --- bq. The result of which is that concurrent read access

[jira] [Commented] (OAK-156) Observation events need Session.refresh

[ https://issues.apache.org/jira/browse/OAK-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410514#comment-13410514 ] Michael Dürig commented on OAK-156: --- In revision 1359763 I added a refresh call each time b

[jira] [Assigned] (OAK-156) Observation events need Session.refresh

[ https://issues.apache.org/jira/browse/OAK-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig reassigned OAK-156: - Assignee: Michael Dürig > Observation events need Session.refresh >

[jira] [Resolved] (OAK-156) Observation events need Session.refresh

[ https://issues.apache.org/jira/browse/OAK-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig resolved OAK-156. --- Resolution: Fixed Fix Version/s: 0.4 Fixed at revision 1359763 > Observation eve

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410364#comment-13410364 ] Stefan Guggisberg commented on OAK-169: --- bq. There is currently no statement about iter

[jira] [Commented] (OAK-74) avoid use of "internal" namespace

[ https://issues.apache.org/jira/browse/OAK-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410341#comment-13410341 ] Julian Reschke commented on OAK-74: --- One way to do this would be to remap this namespace nam

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410332#comment-13410332 ] Michael Dürig commented on OAK-169: --- Thanks for digging this up. Citing from that message:

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410324#comment-13410324 ] Stefan Guggisberg commented on OAK-169: --- FWIW: here's the relevant discussion on the oa

[jira] [Commented] (OAK-175) MemoryNodeStateBuilder inefficient for large child node lists

[ https://issues.apache.org/jira/browse/OAK-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410252#comment-13410252 ] Michael Dürig commented on OAK-175: --- Thanks Jukka, that's great stuff. It only solves half

buildbot success in ASF Buildbot on oak-trunk

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/110 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp

Re: buildbot failure in ASF Buildbot on oak-trunk

On 10.7.12 12:06, Jukka Zitting wrote: Hi, On Tue, Jul 10, 2012 at 12:58 PM, 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/109 Tests in error: testBlobs[1]

Re: buildbot failure in ASF Buildbot on oak-trunk

Hi, On Tue, Jul 10, 2012 at 12:58 PM, 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/109 Tests in error: testBlobs[1](org.apache.jackrabbit.mk.test.MicroKe

[jira] [Resolved] (OAK-177) Too fast timeout in MicroKernelIT.waitForCommit

[ https://issues.apache.org/jira/browse/OAK-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved OAK-177. --- Resolution: Fixed Fix Version/s: 0.4 Assignee: Jukka Zitting Fixed in 1359596.

buildbot failure in ASF Buildbot on oak-trunk

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/109 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp: [

Re: Build failed in Jenkins: oak #31

Hi, On Tue, Jul 10, 2012 at 12:06 PM, wrote: > Failed tests: waitForCommit[1](org.apache.jackrabbit.mk.test.MicroKernelIT) That's a timing problem in the waitForCommit test, see OAK-177. I'm on it. PS. I shut down my cloudbees jenkins build now, as unlike our Buildbot and Travis builds it ca

[jira] [Created] (OAK-177) Too fast timeout in MicroKernelIT.waitForCommit

Jukka Zitting created OAK-177: - Summary: Too fast timeout in MicroKernelIT.waitForCommit Key: OAK-177 URL: https://issues.apache.org/jira/browse/OAK-177 Project: Jackrabbit Oak Issue Type: Bug

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410219#comment-13410219 ] Michael Dürig commented on OAK-169: --- BTW: the stable order guarantee has disappeared from t

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410207#comment-13410207 ] Thomas Mueller commented on OAK-169: Again about linked list: Jukkas has a point that a r

Build failed in Jenkins: oak #31

See Changes: [jukka] OAK-12: Implement a test suite for the MicroKernel Clear fields in MK integration tests to avoid extra memory use with JUnit [jukka] OAK-176: Reduce CoreValueFactoryImpl footprint [mduerig] JCR-3376: TCK: SQLPathTest.test

Re: buildbot failure in ASF Buildbot on oak-trunk

Hi, On Tue, Jul 10, 2012 at 11:42 AM, Michael Dürig wrote: > On 10.7.12 10:25, Jukka Zitting wrote: >> Looks like we may need to increase the heap size available at least to >> integration tests. > [...] > Should I change the heap size to 256M? Actually, as recently discussed, it seems like JUni

Re: buildbot success in ASF Buildbot on oak-trunk

Hmm the previous failure might as well be transient. Let's wait and see before we increase heap settings. Michael On 10.7.12 10:47, build...@apache.org wrote: The Buildbot has detected a restored build on builder oak-trunk while building ASF Buildbot. Full details are available at: http:/

[jira] [Resolved] (OAK-176) Reduce CoreValueFactoryImpl footprint

[ https://issues.apache.org/jira/browse/OAK-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved OAK-176. --- Resolution: Fixed Done in revision 1359541. > Reduce CoreValueFactoryImpl footprint > -

[jira] [Updated] (OAK-176) Reduce CoreValueFactoryImpl footprint

[ https://issues.apache.org/jira/browse/OAK-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated OAK-176: -- Fix Version/s: 0.4 > Reduce CoreValueFactoryImpl footprint > - > >

buildbot success in ASF Buildbot on oak-trunk

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/107 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp

Re: buildbot failure in ASF Buildbot on oak-trunk

On 10.7.12 10:25, Jukka Zitting wrote: Hi, On Tue, Jul 10, 2012 at 11:21 AM, 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/106 Tests in error: testBlobs[1

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410174#comment-13410174 ] Michael Dürig commented on OAK-169: --- Support for (efficient) stable order would require sup

Re: buildbot failure in ASF Buildbot on oak-trunk

Hi, On Tue, Jul 10, 2012 at 11:21 AM, 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/106 Tests in error: testBlobs[1](org.apache.jackrabbit.mk.test.MicroKe

[jira] [Created] (OAK-176) Reduce CoreValueFactoryImpl footprint

Jukka Zitting created OAK-176: - Summary: Reduce CoreValueFactoryImpl footprint Key: OAK-176 URL: https://issues.apache.org/jira/browse/OAK-176 Project: Jackrabbit Oak Issue Type: Improvement

buildbot failure in ASF Buildbot on oak-trunk

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/106 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp: [

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410127#comment-13410127 ] Carsten Ziegeler commented on OAK-169: -- My uses cases would work ootb, if the nodes are

[jira] [Commented] (OAK-169) Support orderable nodes

[ https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410110#comment-13410110 ] Thomas Mueller commented on OAK-169: Could we discuss this in the next meeting? I think o