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

[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] Please review, nunc-stans 63 and 64

[William Brown]

https://fedorahosted.org/nunc-stans/ticket/63

https://fedorahosted.org/nunc-stans/attachment/ticket/63/0001-Ticket-63-segfault-in-thr_stack_create.patch

https://fedorahosted.org/nunc-stans/ticket/64

https://fedorahosted.org/nunc-stans/attachment/ticket/64/0001-Ticket-64-Remove-ns_job_modify.patch


-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane


signature.asc
Description: This is a digitally signed message part
___
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 #1085

[jenkins]

See 

Changes:

[William Brown] Ticket 48986 - 47808 triggers overflow in uiduniq.c

[William Brown] Ticket 48982 - Enabling a plugin that has a versioned so causes 
overflow

--
Started by an SCM change
Building remotely on F23 (fedora Fedora23 Fedora fedora23) in workspace 

Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git://git.fedorahosted.org/git/389/ds.git
 > git init  # 
 > timeout=10
Fetching upstream changes from git://git.fedorahosted.org/git/389/ds.git
 > git --version # timeout=10
 > git -c core.askpass=true 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 --add 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 -c core.askpass=true 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 31c0425599b13e492cdadff5ea64da6e1696b6bc (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 31c0425599b13e492cdadff5ea64da6e1696b6bc
 > git rev-list 04a9c896a99be843e531f989352f39687518c4e8 # timeout=10
[389-ds-base] $ /bin/sh -e /tmp/hudson1260275096046719726.sh

Running configure...
CFLAGS= -Wall CXXFLAGS= -Wall ./configure --with-tmpfiles-d=/etc/tmpfiles.d 
--with-openldap --enable-autobind --enable-gcc-security --with-selinux 
--with-systemdsystemunitdir=/lib/systemd/system 
--with-systemdsystemconfdir=/etc/systemd/system --enable-debug
Build log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1085.txt

Running make...
Build log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1085.txt

Checking for warnings...
Build http://jenkins.fedorainfracloud.org/job/389-ds-base/1085/ failed
There are build warnings
Warning log is 
http://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build-warns.1085.txt
Last 100 lines of warning log:

ldap/servers/slapd/fedse.c:1951:15: warning: unused variable ‘resolved_path’ 
[-Wunused-variable]


Build step 'Execute shell' marked build as failure
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Re: Please review design proposal for tickets 47986 and 48976

[Noriko Hosoi]

Hi Ludwig,

On 09/29/2016 05:43 AM, Ludwig Krispenz wrote:

This is the initial proposal, thanks for your feedback

http://www.port389.org/docs/389ds/design/delay-accepting-updates-after-init.html 




Please help me understanding the design...

I'm having a bit hard time to figure out the relationship/dependency 
among these 3 config parameters.


nsslapd-replica-accept-updates-state: on/off
nsslapd-replica-accept-updates-delay: -1/0/n
nsslapd-replica-accept-updates-auto: on/off

Are they independent or dependent?  Do they take any combinations -- 2 * 
3 * 2 == 12.  There are 12 different behaviors?  (assuming n for -delay 
is one case :)


What is your recommendation to the customers?  I mean, what is the 
default setting?  For instance, if -auto is "on", when an online init is 
executed on the master, the scenario is automatically kicked in?


Thanks,
--noriko





||

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Please review design proposal for tickets 47986 and 48976

[Ludwig Krispenz]

This is the initial proposal, thanks for your feedback

http://www.port389.org/docs/389ds/design/delay-accepting-updates-after-init.html

--
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org