Hi Stefan,
On 08/07/2019 09:05, Stefan Seelmann wrote:
Hi,
I see two types of test issues recently:
* DIRSERVER_1974_IT seems to take too long on slow machines (especially
Windows) and causes timeout. I'll investigate a bit further.
This test - which was ignored because it was failing - injects 1000
entries into a server. It will also remove those 1000 entries. That will
take a heck of time if done on a slow machine with a HD. We can safely
@Ignore it again as soon as the associated bug was fixed.
* ClientAddRequestTest sometimes hangs forever. I was able to reproduce
on my machine when running it multiple times. It waits forever for a
future, see thread dump below.
I'll investigate this one.
Kind Regards,
Stefan
"main" #1 prio=5 os_prio=0 tid=0x00007fd6a400d800 nid=0x73ce in
Object.wait() [0x00007fd6aa16e000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007794c4780> (a
org.apache.directory.ldap.client.api.future.AddFuture)
at
org.apache.directory.ldap.client.api.future.UniqueResponseFuture.get(UniqueResponseFuture.java:90)
- locked <0x00000007794c4780> (a
org.apache.directory.ldap.client.api.future.AddFuture)
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.add(LdapNetworkConnection.java:1089)
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.add(LdapNetworkConnection.java:1021)
at
org.apache.directory.shared.client.api.operations.ClientAddRequestTest.testAddNullValueSchemaAware(ClientAddRequestTest.java:417)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
