See <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/465/changes>
Changes:
[Noriko Hosoi] Ticket #47935 - Error: failed to open an LDAP connection to host 'example.org' port '389' as user 'cn=Directory Manager'. Error: unknown.
[Mark Reynolds] Ticket 47451 - Dynamic Plugin - various fixes
------------------------------------------
Started by an SCM change
Building remotely on Fedora20 in workspace <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/>
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git://git.fedorahosted.org/git/389/ds.git
> git init <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/> # timeout=10
Fetching upstream changes from git://git.fedorahosted.org/git/389/ds.git
> git --version # timeout=10
> git fetch --tags --progress git://git.fedorahosted.org/git/389/ds.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url git://git.fedorahosted.org/git/389/ds.git # timeout=10
> git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url git://git.fedorahosted.org/git/389/ds.git # timeout=10
Fetching upstream changes from git://git.fedorahosted.org/git/389/ds.git
> git fetch --tags --progress git://git.fedorahosted.org/git/389/ds.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision ff023a48b7fc78711eed8ae11e67057597acdeb3 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f ff023a48b7fc78711eed8ae11e67057597acdeb3
> git rev-list 4a5eee63f45ed290375440827c92af9b2347a177 # timeout=10
[389-ds-base] $ /bin/sh -e /tmp/hudson5260080722915181296.sh
Running configure...
CFLAGS= -Wall CXXFLAGS= -Wall ./configure --with-tmpfiles-d=/etc/tmpfiles.d --with-openldap --enable-autobind --with-selinux --with-systemdsystemunitdir=/lib/systemd/system --with-systemdsystemconfdir=/etc/systemd/system --enable-debug
Build log is http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/build.2014-12-16_…
Running make...
Build log is http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/build.2014-12-16_…
Checking for warnings...
Build http://jenkins.cloud.fedoraproject.org/job/389-ds-base/465/ failed
There are build warnings
Warning log is http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/build-warns.2014-…
Last 100 lines of warning log:
------------------------------------------------------------
ldap/servers/plugins/uiduniq/uid.c:1288:18: warning: unused variable 'plugin_entry' [-Wunused-variable]
ldap/servers/plugins/uiduniq/uid.c:1315:34: warning: unused variable 'config' [-Wunused-variable]
ldap/servers/plugins/dna/dna.c:2409:29: warning: format '%d' expects argument of type 'int', but argument 4 has type 'PRUint64' [-Wformat=]
ldap/servers/plugins/dna/dna.c:2409:29: warning: format '%d' expects argument of type 'int', but argument 5 has type 'PRUint64' [-Wformat=]
ldap/servers/plugins/dna/dna.c:3419:53: warning: format '%d' expects argument of type 'int', but argument 4 has type 'PRUint64' [-Wformat=]
ldap/servers/plugins/dna/dna.c:3419:53: warning: format '%d' expects argument of type 'int', but argument 5 has type 'PRUint64' [-Wformat=]
ldap/servers/plugins/dna/dna.c:3686:53: warning: format '%d' expects argument of type 'int', but argument 4 has type 'PRUint64' [-Wformat=]
ldap/servers/plugins/dna/dna.c:3686:53: warning: format '%d' expects argument of type 'int', but argument 5 has type 'PRUint64' [-Wformat=]
------------------------------------------------------------
Build step 'Execute shell' marked build as failure
Hello,
The tickethttps://fedorahosted.org/389/ticket/47942 was already
reviewed by Mark, Rich and pj101.
The new patch is taking into account the following points:
* incorrect indentation
* Window/Pause configuration attribute are common to total and
incremental updates
* Improve the logging so that when flow control is triggered it is
not too noisy.
With normal logging level, it writes as FATAL the first flow
control event (total or incremental).
If there are others during the session it logs the total
numbers of flow control.
https://fedorahosted.org/389/attachment/ticket/47942/0004-Ticket-47942-DS-h…
I opened the ticket https://fedorahosted.org/389/ticket/47975 for
further improvements of flow control:
* Better default values and procedure to tune them
* Automatic tuning (based on consumer processing rate)
* ability to monitor the flow control events
Thanks
theirry
Hello,
This bug fix (https://fedorahosted.org/389/ticket/47942) was already
reviewed by Mark.
Taking into account a first remark, I change the indentation of the
previous fix (IDE are sometime teasing friends :-) ).
https://fedorahosted.org/389/attachment/ticket/47942/0002-Ticket-47942-DS-h…
The second remark was that the same bug applies both to incremental
and total update. The fix above addressed total update.
The fix below addresses the incremental update.
https://fedorahosted.org/389/attachment/ticket/47942/0003-Ticket-47942-DS-h…
In that last patch, window/pause are hardcoded (100/2s). I was
unsure if the adding new configuration attribute was valuable.
The consequences of this bug for incremental update is less critical
than for total update. With incremental, the RA will hang for
idletimout but then a next replication session will continue sending
updates. While for total update, this bug is fatal.
It is also less likely to occurs (amount of transfert data
(update/entries), job to do on consumer side to apply the update,
#update to send (#update < #entries).
thanks
thierry