[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-14 Thread William Brown
On Wed, 2017-03-15 at 03:37 +, Ankit Yadav wrote: > output of rpm -qa | grep lib389 ==> python-lib389-1.0.2-3.fc25.noarch You should erase this package, it's probably the source of some of your issues. > pid = pid_from_file(self.ds_paths.pid_file) > lib389/paths.py:153: in __getattr__

[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-14 Thread Ankit Yadav
output of rpm -qa | grep lib389 ==> python-lib389-1.0.2-3.fc25.noarch I followed your steps mentioned above but got the same error while running ==> sudo PYTHONPATH=`pwd` py.test -s lib389/tests/cli/conf_backend.py. Then I cloned the latest lib389-master and build the rpm, installed both rpm p

[389-devel] please review: allow ds and lib389 to work with schema in 1.3.6

2017-03-14 Thread William Brown
https://pagure.io/389-ds-base/issue/49172 https://pagure.io/389-ds-base/issue/raw/files/c31ec8fd731b2c66dad5c91e80838cd6404eface75db88844832be40a9d56ff1-0001-Ticket-49172-Allow-lib389-to-read-system-schema-and-.patch https://pagure.io/389-ds-base/issue/raw/files/c804231cbd852551b7eb65eaea3fb37759

[389-devel] Jenkins build is back to normal : 389-ds-base #1213

2017-03-14 Thread jenkins
See ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Build failed in Jenkins: 389-ds-base #1212

2017-03-14 Thread jenkins
See Changes: [William Brown] Ticket 49171 - Nunc Stans incorrectly reports a timeout -- Started by an SCM change Building remotely on F25 (Fedora25 fedora Fedora fedora25) in workspace

[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-14 Thread William Brown
On Tue, 2017-03-14 at 13:32 +, Ankit Yadav wrote: > I solved the error in /lib389/__init__.py line number 526 was > > this code ==> self.inst = self.serverid at line 526 was above this code ==> > self.serverid = args.get(SER_SERVERID_PROP, None). Now here we someone has > tried to assign

[389-devel] urgent: please review, nunc-stans timeout is not correctly handled

2017-03-14 Thread William Brown
https://pagure.io/389-ds-base/issue/49171 https://pagure.io/389-ds-base/issue/raw/files/1b2ca3d697463730a0e867be14206b5ad5155073c6f7dcead57258adb2a56463-0001-Ticket-49171-Nunc-Stans-incorrectly-reports-a-timeou.patch -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

[389-devel] Jenkins build is back to normal : 389-ds-base #1211

2017-03-14 Thread jenkins
See ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Build failed in Jenkins: 389-ds-base #1210

2017-03-14 Thread jenkins
See Changes: [Mark Reynolds] Issue 49170 - sync plugin thread count not handled correctly -- Started by an SCM change Building remotely on F25 (Fedora25 fedora Fedora fedora25) in workspac

[389-devel] please review: Issue 49170 - content sync plugin hangs server shutdown if connections get aborted.

2017-03-14 Thread Mark Reynolds
https://pagure.io/389-ds-base/issue/49170 https://pagure.io/389-ds-base/issue/raw/files/fa65567591599905f6ddf3448efbcfb88386e86562b9169fd4783437417ee7c5-0001-Issue-49170-sync-plugin-thread-count-not-handled-cor.patch ___ 389-devel mailing list -- 389-dev

[389-devel] please review: Issue 49169 - Fix covscan errors

2017-03-14 Thread Mark Reynolds
https://pagure.io/389-ds-base/issue/49169 https://pagure.io/389-ds-base/issue/raw/files/cf6a5bd9440c7d74aac370c116e0c2f84f8c2bd84a2e9f6ba20a0380a6386c3d-0001-Issue-49169-FIx-covscan-errors.patch ___ 389-devel mailing list -- 389-devel@lists.fedoraproject

[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-14 Thread Ankit Yadav
I solved the error in /lib389/__init__.py line number 526 was this code ==> self.inst = self.serverid at line 526 was above this code ==> self.serverid = args.get(SER_SERVERID_PROP, None). Now here we someone has tried to assign self.serverid to self.inst before self.serverid has been assig

[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-14 Thread Ankit Yadav
I tried to run test cases got this output: 5 failed, 28 passed, 42 error in 101.93 seconds obviously the output was quite long above line is just the summary. detailed output is here https://drive.google.com/open?id=1fbNXTH_tTjHwdl6ZWE_-4QsnOzI8J97oGxr0KZmFmkE Is this normal or there is someth

[389-devel] Build failed in Jenkins: 389-ds-base #1209

2017-03-14 Thread jenkins
See Changes: [William Brown] Ticket 49154 - Nunc Stans stress should assert it has 95% success rate [William Brown] Ticket 49164 - Change NS to acq-rel semantics for atomics -- Started b