[
https://issues.apache.org/jira/browse/JCR-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3411.
-
Resolution: Later
> UserManager createUser method without Principal
>
[
https://issues.apache.org/jira/browse/JCR-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela closed JCR-4050.
---
> Allow creation of users with existing password hashes in UserManager
>
[
https://issues.apache.org/jira/browse/JCR-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-4050:
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
i am sorry, but that request doesn't sound
Hi,
I assume that at least some of the tests that sporadically fail on the
Apache Jenkins fail because of timing issues. To address this we could
either
a) skip these tests on Jenkins,
b) increase the time-out,
c) apply platform dependent time-outs.
I would prefer b). I presume that there
>>
>>But agreed, this is a bug and we should fix it.
>>
>Actually, I'm not too sure as long as we concretely document the
>behavior and potentially have a sample abstract
>commit-creator/listener which does the job well (may be similar to the
>hack I used)
I've created OAK-5740 and attached test
Hi,
For re-indexing, there are two problems actually:
* Indexing can take multiple days, so resume would be nice
* For synchronous indexes, indexing create a large commit, which is
problematic (specially for MongoDB)
To solve both problems ("kill two birds with one stone"), we could instead
try
Hi,
>No I actually meant getting individual time-out values (or a scaling
>factor for time-outs) from CIHelper. That class already provides the
>means to skip tests based on where they are running. So it should be
>relatively straight forward to have it supply scaling factors for
>time-outs in a
Hi,
I assume with (b) you mean: change tests to use loops, combined with very
high timeouts. Example:
Before:
save();
Thread.sleep(1000);
assertTrue(abc());
After:
save();
for(int i=0; !abc() && i<600; i++) {
Thread.sleep(100);
}
assertTrue(abc());
The
Hi,
If in this context b) actually means 'fix the tests to be more lenient' I
agree this should be the way to go.
However I think the failing tests are not being given enough priority
currently and if people aren't able to carve out the time for
investigation, then it means we're stuck with very
On 21.02.17 14:09, Thomas Mueller wrote:
Hi,
I assume with (b) you mean: change tests to use loops, combined with very
high timeouts. Example:
No I actually meant getting individual time-out values (or a scaling
factor for time-outs) from CIHelper. That class already provides the
means to
On 21.02.17 15:32, Alex Parvulescu wrote:
Hi,
If in this context b) actually means 'fix the tests to be more lenient' I
agree this should be the way to go.
Yes and this is not necessarily bad as I presume that some of the
time-outs might well be overly tight (at least in some
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1441)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1441/ to view
the results.
Changes:
[reschke] OAK-5738: Potential NPE in LargeLdapProviderTest
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1442)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1442/ to view
the results.
Changes:
[reschke] OAK-5738: Potential NPE in LargeLdapProviderTest
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1444)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1444/ to view
the results.
Changes:
[reschke] OAK-5738: Potential NPE in LargeLdapProviderTest
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1443)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1443/ to view
the results.
Changes:
[reschke] OAK-5738: Potential NPE in LargeLdapProviderTest
15 matches
Mail list logo
