Actually, this performance tax can be avoided. We creata a temporary KeyStore for every single test class, when we would only need it for the tests related to TLS. We could use a common KeyStore that is added to the class resources, and avoid creating it. That would speed up the tests quite a bit, I think (we are talking about minutes saved, not seconds !)

On 21/06/2019 16:50, Emmanuel Lécharny wrote:
Just FTR,

on my mac, the server-integ tests are taking forever to be completed (around 10s per class). It seems it's due to the InetAddress.getLocalHost() call done in the CertificateUtil.setInfo() method, which now takes around 5 seconds to complete. It's related to some change made in the JDK for Mac OSX (https://bugs.openjdk.java.net/browse/JDK-8136913 and https://bugs.openjdk.java.net/browse/JDK-8080819).

We probably can speed these tests up by changing the way we generate the certificate.


On 20/06/2019 17:31, Emmanuel Lécharny wrote:
Hi !


for those who are following what's going on at Directory, and especially those trying to extend the project (thinking about Raju), we are currently working hard trying to close a LDAP API release, ApacheDS release, and Studio release. This comes with a price to pay: a bit of instability, a lot of git pull and some associated burden.

The LDAP API project is pretty much in good shape. We had a release a couple of weeks ago, and some other changes are under way. We could pretty well be able to cut a 2.0.0-RC1 soon.

ApacheDS is in a more complex situation. There are 391 opened issues (most of them are already postponed to 2.1: 250 actually). If we focus on issues opened for 2.0.0.AM26, we are taking about 30 issues, 121 if we include 2.0.0-RC1. This is a loty of work, but we have already fixed more or less 30 issues in the last 2 weeks.

Stefan is trying his best to follow up - and is pretty successful in that, considering all the pain we create for him ;-) -and Studio is also in a good shape.Hopefully, it will be released very soon after ApacheDS and LDAP-API will be released.

Fortress migration to 2.0 should not be that problematic.


I expect that in the coming weeks we will be able to have a decent ApacheDS release, with fixed installers (this is the main burden atm).

That's it, feel free to add something to what I just wrote, Stefan, Colm, Shawn or anyone !


Emmanuel


---------------------------------------------------------------------
To unsubscribe, e-mail: api-unsubscr...@directory.apache.org
For additional commands, e-mail: api-h...@directory.apache.org

Reply via email to