Build Update for apache/jackrabbit-oak
-
Build: #1539
Status: Fixed
Duration: 31 minutes and 14 seconds
Commit: 9dc09b8 (trunk)
Author: Angela Schreiber
Message: OAK-527: permissions (wip, clean up)
git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/t
Build Update for apache/jackrabbit-oak
-
Build: #1536
Status: Still Failing
Duration: 41 minutes and 9 seconds
Commit: 248fe12 (trunk)
Author: Angela Schreiber
Message: OAK-50 : Implement User Management (wip)
git-svn-id: https://svn.apache.org/repos/asf/jac
Build Update for apache/jackrabbit-oak
-
Build: #1535
Status: Still Failing
Duration: 45 minutes and 56 seconds
Commit: b30b873 (trunk)
Author: Angela Schreiber
Message: OAK-51 : Access Control Management (wip)
git-svn-id: https://svn.apache.org/repos/asf/jack
Build Update for apache/jackrabbit-oak
-
Build: #1534
Status: Still Failing
Duration: 30 minutes and 0 seconds
Commit: 55073d6 (trunk)
Author: Alexandru Parvulescu
Message: OAK-819 Lucene fulltext on node not working properly - marking failing
tests
git-svn-i
Build Update for apache/jackrabbit-oak
-
Build: #1533
Status: Still Failing
Duration: 29 minutes and 54 seconds
Commit: 20e1277 (trunk)
Author: Alexandru Parvulescu
Message: OAK-819 Lucene fulltext on node not working properly - marking failing
tests
git-svn-
Build Update for apache/jackrabbit-oak
-
Build: #1532
Status: Still Failing
Duration: 34 minutes and 54 seconds
Commit: f56c447 (trunk)
Author: Alexandru Parvulescu
Message: OAK-821 UserImportTest.testImportGroupIntoUsersTree failing
git-svn-id: https://svn.ap
I've created OAK-821 for this failed test, next I'll try mark the lucene
failures as known issues
On Tue, May 14, 2013 at 4:08 PM, Travis CI wrote:
> Build Update for apache/jackrabbit-oak
> -
>
> Build: #1531
> Status: Still Failing
>
> Duration: 26 minutes a
Hi,
On Tue, May 14, 2013 at 4:55 PM, Alex Parvulescu
wrote:
> As previously stated (on Jukka's reference discussion) I think we need to
> see the failures each time, otherwise we don't react accordingly.
Do we have evidence of cases where we haven't reacted accordingly
after the first failure no
Build Update for apache/jackrabbit-oak
-
Build: #1531
Status: Still Failing
Duration: 26 minutes and 36 seconds
Commit: d660a99 (trunk)
Author: Marcel Reutegger
Message: Always send failure notifications
git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/
hi,
I fully agree with Marcel.
As previously stated (on Jukka's reference discussion) I think we need to
see the failures each time, otherwise we don't react accordingly.
The proper way to handle a failure is to create a jira issue and mark the
test as ignored, this practice also keeps the noise
Hi,
On Tue, May 14, 2013 at 4:36 PM, Marcel Reutegger wrote:
> the last travis notification I got via the oak-dev list was from yesterday
> for a
> successful build [0]. travis is broken or this is due to how we configure the
> travis build. all builds after 1521 failed [1] and I really think it
hi,
the last travis notification I got via the oak-dev list was from yesterday for a
successful build [0]. travis is broken or this is due to how we configure the
travis build. all builds after 1521 failed [1] and I really think it's better
we get
notifications for every failure and not just when
hi,
I see a test failing recently: UserImportTest.testImportGroupIntoUsersTree
I'm not really sure why/when this started happening, I'll create an issue
and mark it as ignored.
The travis CI build don't show it but it also missed the lucene tests that
are failing so we might want to take another
Hi,
On Mon, May 6, 2013 at 7:57 PM, Jukka Zitting wrote:
> Please vote on releasing this package as Apache Jackrabbit Oak 0.7.
The vote passes as follows:
+1 Alex Parvulescu
+1 Claus Köll
+1 Jukka Zitting
+1 Julian Reschke
Thanks! I'll push the release out.
BR,
Jukka Zitting
14 matches
Mail list logo