Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

2016-06-10 Thread Kremmyda, Olympia (Nokia - GR/Athens)
Devel <gluster-devel@gluster.org> Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6 On Thu, Jun 09, 2016 at 09:39:29AM +, Kremmyda, Olympia (Nokia - GR/Athens) wrote: > Hi, > > Is there any update on this issue? Not really. This fa

Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

2016-06-09 Thread Niels de Vos
evel-boun...@gluster.org > [mailto:gluster-devel-boun...@gluster.org] On Behalf Of Atin Mukherjee > Sent: Friday, May 20, 2016 7:11 PM > To: Emmanuel Dreyfus <m...@netbsd.org> > Cc: Gluster Devel <gluster-devel@gluster.org> > Subject: Re: [Gluster-devel] netbsd smoke tests fail

Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

2016-06-09 Thread Kremmyda, Olympia (Nokia - GR/Athens)
> Subject: Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6 No, we didn't solve this problem yet. Niels had a patch up for review to fix it but unfortunately it didn't. Kaushal also tried to reproduce it on a netbsd machine, but nothing failed for

Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

2016-05-20 Thread Emmanuel Dreyfus
On Fri, May 20, 2016 at 05:43:07PM +0300, Angelos SAKELLAROPOULOS wrote: > May I ask why following review requests are not submitted to release-3.6 ? > It seems that they fail in netbsd, freebsd smoke tests which are not > related to code changes. There are build errors. I am note sur how you

Re: [Gluster-devel] netbsd smoke tests fail when code patches are backported to release-3.6

2016-05-20 Thread Ravishankar N
On 05/20/2016 08:13 PM, Angelos SAKELLAROPOULOS wrote: Hi, May I ask why following review requests are not submitted to release-3.6 ? It seems that they fail in netbsd, freebsd smoke tests which are not related to code changes. You'd have to re-trigger tests if they are spurious failures.