[Gluster-infra] [Gluster-devel] NetBSD regressions not being triggered for patches

Nithya Balachandran nbalacha at redhat.com
Wed Jun 17 08:58:19 UTC 2015


----- Original Message -----
> From: "Avra Sengupta" <asengupt at redhat.com>
> To: "Rajesh Joseph" <rjoseph at redhat.com>, "Kaushal M" <kshlmster at gmail.com>
> Cc: "Gluster Devel" <gluster-devel at gluster.org>, "gluster-infra" <gluster-infra at gluster.org>
> Sent: Wednesday, June 17, 2015 1:42:25 PM
> Subject: Re: [Gluster-devel] [Gluster-infra] NetBSD regressions not being triggered for patches
> 
> On 06/17/2015 12:12 PM, Rajesh Joseph wrote:
> >
> > ----- Original Message -----
> >> From: "Kaushal M" <kshlmster at gmail.com>
> >> To: "Emmanuel Dreyfus" <manu at netbsd.org>
> >> Cc: "Gluster Devel" <gluster-devel at gluster.org>, "gluster-infra"
> >> <gluster-infra at gluster.org>
> >> Sent: Wednesday, 17 June, 2015 11:59:22 AM
> >> Subject: Re: [Gluster-devel] [Gluster-infra] NetBSD regressions not being
> >> triggered for patches
> >>
> >> cloud.gluster.org is served by Rackspace Cloud DNS. AFAICT, there is
> >> no readily available option to do zone transfers from it. We might
> >> have to contact the Rackspace support to find out if they can do it as
> >> a special request.
> >>
> > If this is going to take time then I prefer not to block patches for
> > NetBSD. We can address
> > any NetBSD regression caused by patches as a separate bug. Otherwise our
> > regression queue will
> > continue to grow.
> +1 for this. We shouldn't be blocking patches for NetBSD regression till
> the infra scales enough to handle the kind of load we are throwing at
> it. Once the regression framework is scalable enough, we can fix any
> regressions (if any) introduced. This will bring down the turnaround
> time, for the patch acceptance.

+1


> >
> >> On Wed, Jun 17, 2015 at 11:50 AM, Emmanuel Dreyfus <manu at netbsd.org>
> >> wrote:
> >>> Venky Shankar <yknev.shankar at gmail.com> wrote:
> >>>
> >>>> If that's the case, then I'll vote for this even if it takes some time
> >>>> to get things in workable state.
> >>> See my other mail about this: you enter a new slave VM in the DNS and it
> >>> does not resolve, or somethimes you get 20s delays. I am convinced this
> >>> is the reason why Jenkins bugs.
> >>>
> >>> --
> >>> Emmanuel Dreyfus
> >>> http://hcpnet.free.fr/pubz
> >>> manu at netbsd.org
> >>> _______________________________________________
> >>> Gluster-infra mailing list
> >>> Gluster-infra at gluster.org
> >>> http://www.gluster.org/mailman/listinfo/gluster-infra
> >> _______________________________________________
> >> Gluster-devel mailing list
> >> Gluster-devel at gluster.org
> >> http://www.gluster.org/mailman/listinfo/gluster-devel
> >>


More information about the Gluster-infra mailing list