Also, I do run the tests, there are just a number that fail because my openldap isn't configured correctly for user and password policy modifications, so I missed that these other ones were failing as well.
----- Original Message ----- From: "Chris Pike" <[email protected]> To: "fortress" <[email protected]> Sent: Thursday, July 13, 2017 8:45:32 AM Subject: Re: Broken Build FC-221 add id to non temporal role constraint... Yeah, I was actually removing a user from a role for one my tests. I added them back in, so this should be resolved now. ----- Original Message ----- From: "Emmanuel Lécharny" <[email protected]> To: [email protected] Sent: Thursday, July 13, 2017 12:31:01 AM Subject: Re: Broken Build FC-221 add id to non temporal role constraint... Le 13/07/2017 à 04:04, Shawn McKinney a écrit : > Chris, it looks like this commit broke the fortress core build: > > https://github.com/apache/directory-fortress-core/commit/995073dacd41cb804eb94b57195d8e9a3de6d6ee > > As evidenced by this jenkins test; > http://mail-archives.apache.org/mod_mbox/directory-notifications/201707.mbox/%3c24304792.10192.1499430533761.JavaMail.jenkins@crius%3e > > I also verified locally by checking out the commit, running junit tests, > getting the errors, checking out the previous commit, no errors. > > Please let me know what you find out. That should be easy to fix : the test counts the number of role, so adding one will break the check on this count. -- Emmanuel Lecharny Symas.com directory.apache.org
