[Gluster-Maintainers] Build failed in Jenkins: experimental-periodic #316

2018-05-09 Thread jenkins 
See 

--
[...truncated 974.31 KB...]
[New LWP 28693]
[New LWP 28691]
[New LWP 28692]
[New LWP 28694]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `glusterd --xlator-option 
management.working-directory=/d/backends/2/glusterd --'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f3f1c40deb4 in xlator_volume_option_get_list 
(vol_list=0xff00, key=0x25b4980 "run-directory") at 
:921
921 if (!vol_list->given_opt) {

Thread 7 (Thread 0x7f3f121a0700 (LWP 28694)):
#0  0x7f3f1b1ff42d in __lll_lock_wait () from /lib64/libpthread.so.0
No symbol table info available.
#1  0x7f3f1b1fadcb in _L_lock_812 () from /lib64/libpthread.so.0
No symbol table info available.
#2  0x7f3f1b1fac98 in pthread_mutex_lock () from /lib64/libpthread.so.0
No symbol table info available.
#3  0x7f3f1c3a6ab4 in gf_log_glusterlog (ctx=0x2560010, domain=0x25aa4b0 
"management", file=0x7f3f10f67a8d "glusterd-svc-mgmt.c", 
function=0x7f3f10f67d90 <__FUNCTION__.25081> "glusterd_svc_stop", line=229, 
level=GF_LOG_INFO, errnum=0, msgid=106568, appmsgstr=0x7f3f0ccaad78, 
callstr=0x0, tv=..., graph_id=0, fmt=gf_logformat_withmsgid) at 
:1454
timestr = "2018-05-09 16:25:41.548332", '\000' 
header = 0x7f3f08007890 "[2018-05-09 16:25:41.548332] I [MSGID: 106568] 
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: "
footer = 0x0
msg = 0x7f3f08002bf0 "[2018-05-09 16:25:41.548332] I [MSGID: 106568] 
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service is 
stopped"
hlen = 105
flen = 0
mlen = 23
ret = 105
#4  0x7f3f1c3a75bd in gf_log_print_plain_fmt (ctx=0x2560010, 
domain=0x25aa4b0 "management", file=0x7f3f10f67a8d "glusterd-svc-mgmt.c", 
function=0x7f3f10f67d90 <__FUNCTION__.25081> "glusterd_svc_stop", line=229, 
level=GF_LOG_INFO, errnum=0, msgid=106568, appmsgstr=0x7f3f0ccaad78, 
callstr=0x0, tv=..., graph_id=0, fmt=gf_logformat_withmsgid) at 
:1690
ret = -1
logger = gf_logger_glusterlog
#5  0x7f3f1c3a8147 in _gf_msg_internal (domain=0x25aa4b0 "management", 
file=0x7f3f10f67a40 
"
 function=0x7f3f10f67d90 <__FUNCTION__.25081> "glusterd_svc_stop", line=229, 
level=GF_LOG_INFO, errnum=0, msgid=106568, appmsgstr=0x7f3f0ccaad78, 
callstr=0x0, graph_id=0) at 
:2028
ret = 0
size = 0
basename = 0x7f3f10f67a8d "glusterd-svc-mgmt.c"
this = 0x25a9480
ctx = 0x2560010
iter = 0x25602f8
buf_tmp = 0x25602f8
buf_new = 0x0
first = 0x0
tv = {tv_sec = 1525883141, tv_usec = 548332}
found = false
flush_lru = false
flush_logged_msg = true
__FUNCTION__ = "_gf_msg_internal"
#6  0x7f3f1c3a851b in _gf_msg (domain=0x25aa4b0 "management", 
file=0x7f3f10f67a40 
"
 function=0x7f3f10f67d90 <__FUNCTION__.25081> "glusterd_svc_stop", line=229, 
level=GF_LOG_INFO, errnum=0, trace=0, msgid=106568, fmt=0x7f3f10f67bf0 "%s 
service is stopped") at 
:2107
ret = 23
msgstr = 0x7f3f080020e0 "bitd service is stopped"
ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 
0x7f3f0ccaae80, reg_save_area = 0x7f3f0ccaada0}}
this = 0x25a9480
ctx = 0x2560010
callstr = '\000' 
passcallstr = 0
log_inited = 1
__PRETTY_FUNCTION__ = "_gf_msg"
#7  0x7f3f10f1471a in glusterd_svc_stop (svc=0x7f3f1c71f340, sig=15) at 
:228
ret = 0
__FUNCTION__ = "glusterd_svc_stop"
#8  0x7f3f10f1b5ce in glusterd_bitdsvc_stop (svc=0x7f3f1c71f340, sig=15) at 
:141
No locals.
#9  0x7f3f10f1b430 in glusterd_bitdsvc_manager (svc=0x7f3f1c71f340, 
data=0x0, flags=2) at 
:88
ret = 0
this = 0x25a9480
__PRETTY_FUNCTION__ = "glusterd_bitdsvc_manager"
__FUNCTION__ = "glusterd_bitdsvc_manager"
#10 0x7f3f10f18103 in

Re: [Gluster-Maintainers] Release 4.1: Branched

2018-05-09 Thread Shyam Ranganathan 
Here is the current release activity calendar,

- RC0 tagging: May 14th
- RC0 builds: May 15th
- May 15th - 25th
  - Upgrade testing
  - General testing and feedback period
- (on need basis) RC1 build: May 26th
- GA readiness call out: May, 28th
- GA tagging: May, 30th
- +2-4 days release announcement

Thanks,
Shyam

On 05/06/2018 09:20 AM, Shyam Ranganathan wrote:
> Hi,
> 
> Release 4.1 has been branched, as it was done later than anticipated the
> calendar of tasks below would be reworked accordingly this week and
> posted to the lists.
> 
> Thanks,
> Shyam
> 
> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote:
>> Hi,
>>
>> As we have completed potential scope for 4.1 release (reflected here [1]
>> and also here [2]), it's time to talk about the schedule.
>>
>> - Branching date (and hence feature exception date): Apr 16th
>> - Week of Apr 16th release notes updated for all features in the release
>> - RC0 tagging: Apr 23rd
>> - Week of Apr 23rd, upgrade and other testing
>> - RCNext: May 7th (if critical failures, or exception features arrive late)
>> - RCNext: May 21st
>> - Week of May 21st, final upgrade and testing
>> - GA readiness call out: May, 28th
>> - GA tagging: May, 30th
>> - +2-4 days release announcement
>>
>> and, review focus. As in older releases, I am starring reviews that are
>> submitted against features, this should help if you are looking to help
>> accelerate feature commits for the release (IOW, this list is the watch
>> list for reviews). This can be found handy here [3].
>>
>> So, branching is in about 4 weeks!
>>
>> Thanks,
>> Shyam
>>
>> [1] Issues marked against release 4.1:
>> https://github.com/gluster/glusterfs/milestone/5
>>
>> [2] github project lane for 4.1:
>> https://github.com/gluster/glusterfs/projects/1#column-1075416
>>
>> [3] Review focus dashboard:
>> https://review.gluster.org/#/q/starredby:srangana%2540redhat.com
>> ___
>> maintainers mailing list
>> maintainers@gluster.org
>> http://lists.gluster.org/mailman/listinfo/maintainers
>>
> ___
> maintainers mailing list
> maintainers@gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
> 
___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers