ver2 belong to same trusted storage pool or not. However, if
one does not have a trusted storage pool access, is it possible to achieve
the same?
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
ef accounting for glfd and only refs were
on fd_t.
No, we don't need this additional reference.
>
> Can an fd returned by this function live more time than the associated
> glfd in some circumstances ?
>
> Also could you please check if it is the second/subsequent fsync_async()
>
On Thu, Nov 10, 2016 at 7:12 AM, Pranith Kumar Karampuri
wrote:
> hi,
> The only problem left was EC taking more time. This should affect
> small files a lot more. Best way to solve it is using compound-fops. So for
> now I think going ahead with the release is best.
>
> We are waiting for R
On 10-Nov-2016 20:52, "Vijay Bellur" wrote:
>
> On Thu, Nov 10, 2016 at 10:16 AM, Manikandan Selvaganesh
> wrote:
> > Enabling/disabling quota or removing limits are the ways in which
quota.conf
> > is regenerated to the later version. It works properly. And as Pranith
said,
> > both enabling/dis
On 11-Nov-2016 11:50, "Mohammed Rafi K C" wrote:
>
> Hi Abhishek,
>
> Could you please see if you are bricks are healthy or not, may be you can
do a gluster volume status or you can look into the logs. If bricks are not
running can you please attach the bricks logs in /var/log/gluster/bricks/ .
>
lock
merging of subset of patches and made it possible to take all 4 in in
one go, we could run tests only on top of these patches. The last time
I checked, such a feature did not exist in Jenkins.
Thanks,
Raghavendra Talur
>
> --
> nigelb
>
> __
ll make it
easier to get to a consensus on what to filter.
For example:
cppcheck.sh
func ignore warnings()
{
for warnings in warning1 \
warning2 \
; do
...
}
This way, developers will have a way to send patches on what to filter
a
On Tue, Jan 24, 2017 at 10:39 AM, Vijay Bellur wrote:
>
>
> On Thu, Jan 19, 2017 at 8:06 AM, Jeff Darcy wrote:
>>
>> > The more relevant question would be with TCP_KEEPALIVE and
>> > TCP_USER_TIMEOUT
>> > on sockets, do we really need ping-pong framework in Clients? We might
>> > need
>> > that i
[1]. You can also find the list of tests [2].
I have filed only one issue in github[3] and that is the only blocker
from testing perspective for this release.
Thanks,
Raghavendra Talur
[1] Components and bad tests against them
<->
afr 1
ec 1
gfapi 2
tier
On Thu, Feb 2, 2017 at 11:08 AM, Nithya Balachandran
wrote:
>
>
> On 2 February 2017 at 09:26, Nithya Balachandran
> wrote:
>>
>>
>>
>> On 1 February 2017 at 19:27, Raghavendra Talur wrote:
>>>
>>> Hi all,
>>>
>>> As we a
On Sun, Mar 12, 2017 at 3:18 PM, Amar Tumballi wrote:
> Please check inline.
>
> On Fri, Mar 10, 2017 at 2:39 PM, Xavier Hernandez
> wrote:
>>
>> Hi,
>>
>> I'm looking at the locks xlator and I see that it has something called
>> reserve locks. I remember long time ago that someone said this was
te replace-brick command for
"distribute only" volumes. It should print out a error "The right way
to replace brick for distribute only volume is to add brick, wait for
rebalance to complete and remove brick" and return a "-1"
On Sun, Apr 16, 2017 at 9:07 PM, Raghavendra Talur wrote:
> I am not able to login even after specifying the key file
>
> $ ssh -T -vvv -i ~/.ssh/gluster raghavendra-ta...@git.gluster.org
> OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
> debug1: Reading configuration data /h
Seems to be fixed now.
On Mon, Apr 17, 2017 at 5:37 AM, Zhengping Zhou
wrote:
> Did anyone encount this problem when excute "git pull", this output is :
>
>
> [zzp@42 gluster]$ git pull
> ssh_exchange_identification: Connection closed by remote host
> fatal: Could not read from remote reposi
3.10 beyond bugs, please update the review, or leave a
comment in the review, for me to pick it up
Thanks,
Raghavendra Talur
[1] Release bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.2
[2] 3.10 review dashboard:
https://review.gluster.org/#/projects/glusterfs,dashb
announcement on 3rd May and we should
have builds/packages ready by then. We will be tagging by tomorrow and
performing a final test with packages before making the announcement.
Thanks,
Raghavendra Talur
On Mon, Apr 17, 2017 at 10:31 AM, Raghavendra Talur wrote:
> Hi,
>
> It's time to prep
On Mon, May 1, 2017 at 3:35 PM, Raghavendra Talur wrote:
> We seem to have merged all the intended patches for 3.10.2 except for
> one. While we wait for [1] to be merged, this is a last chance for
> others to point out if any patch is missing. I have verified that no
> backports ar
tin to assign bug 1447608 to someone. I will
wait for the fix for 3.10.2.
Thanks,
Raghavendra Talur
>
> Nithya
>>
>> Let's get a bug going, and not wait for someone to report it in bugzilla,
>> and also mark it as blocking 3.10.2 release tracker bug.
>>
>> Thank
tomorrow.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1447608
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
idempotent operation which can be run before starting
glusterd service in a container.
Am I right?
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
/release-3.10/doc/release-notes/3.10.2.md
Thanks,
Raghavendra Talur
NOTE: Tracker bug for 3.10.2 will be closed in a couple of days and
tracker for 3.10.3 will be opened, and an announcement for 3.10.3 will
be sent with the details
On Wed, May 3, 2017 at 3:46 PM, Raghavendra Talur wrote:
> I
*enforce* submit order. However, with rebase if necessary it might.
Nigel, would it be possible for you to setup a test server to try?
Thanks,
Raghavendra Talur
[1] http://lists.gluster.org/pipermail/gluster-devel/2016-January/047740.html
>
> _
On Fri, May 26, 2017 at 9:55 PM, Shyam wrote:
> Or this one: https://review.gluster.org/15036
>
> This is backported to 3.8/10 and 3.11 and considering the size and impact of
> the change, I wanted to be sure that we are going to accept this across all
> 3 releases?
>
> @Du, would like your though
/release-3.10/doc/release-notes/3.10.3.md
Thanks,
Raghavendra Talur
NOTE: Tracker bug for 3.10.3 will be closed in a couple of days and
tracker for 3.10.4 will be opened, and an announcement for 3.10.4 will
be sent with the details
___
Gluster-devel mailing
d.g.o.
(GlusterFS 3.11.X packages for Fedora 26 are on d.g.o.) GlusterFS
3.10.X packages are also available for Trusty in the Launchpad PPA. I
will update the table at [1] to reflect the actual state ASAP.
[3] https://download.gluster.org/pub/gluster/glusterfs/3.10/3.10.3/
Thanks,
Raghavendra Talu
d get
these going
3) Empty release notes are posted here [3], if there are any specific
call outs for 3.10 beyond bugs, please update the review, or leave a
comment in the review, for me to pick it up
Thanks,
Raghavendra Talur
[1] Release bug tracker:
https://bugzilla.redhat.com/show_bug.c
Virtual memory data, resident memory is very nicely at 40 MB
after 14 bricks.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
On Tue, Jun 20, 2017 at 8:13 PM, Jeff Darcy wrote:
>
>
>
> On Tue, Jun 20, 2017, at 08:45 AM, Raghavendra Talur wrote:
>
> Here is the data I gathered while debugging the considerable increase in
> memory consumption by brick process when brick multiplexing is on.
>
>
On 21-Jun-2017 9:45 AM, "Jeff Darcy" wrote:
On Tue, Jun 20, 2017, at 03:38 PM, Raghavendra Talur wrote:
Each process takes 795MB of virtual memory and resident memory is 10MB each.
Wow, that's even better than I thought. I was seeing about a 3x difference
per brick (plus th
Adding gluster-devel
On Fri, Jun 23, 2017 at 5:52 PM, Raghavendra Talur wrote:
> Hi All,
>
> Kubernetes and Openshift have amazing projects called minikube and
> minishift which make it very easy to setup those distributed systems
> for easy development. As the Gluster ecosystem
not determine if only tests have been added. It just makes
sure we exit after running updated/added tests and don't run other
tests.
Nigel, you will have to check for "test only change* in jenkins and
conditionally call run-tests.sh with -H
[1] https://review.gluster.org/#/c/13439
_SET_FSID is undefined in line
https://github.com/gluster/glusterfs/blob/master/xlators/storage/posix/src/posix.c#L65
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
On Mon, Sep 25, 2017 at 10:17 PM, Luis Pabon wrote:
> Hi community,
> It has been a great time working together on GlusterFS and Heketi these
> past few years. I remember starting on Heketi to enable GlusterFS for
> Manila, but now I will be moving on to work at Portworx and their
> containerize
On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan wrote:
> Hi,
>
> Recently I was in some conversations that mentioned having to hunt for the
> mail that announced the blocker bug for a release, when there is a need to
> mark a bug as a blocker for that release.
>
> This need not be done as here
n
> then looking at that bug in bugzilla provides the information, if the query
> is more along what all are fixed, the release notes inform regarding the
> same.
>
> As a result, marking all bugs against the tracker, is more work for a
> contributor as well as the release maintainer
On Wed 21 Mar, 2018, 3:57 PM Csaba Henk, wrote:
> Hi list,
>
> We have an ancient hack that fuse not
> just passes on the statvfs data it's getting
> from the storage, but tweaks it by setting
> f_bsize / f_frsize to values of its own
> preference. [1]
>
> The supposed advantage is that f_bsize
>
ly choose the mount option.
The above line holds true for smoke, functional, regression and performance
categories.
If your question is regarding integration testing, it would depend entirely
on how the outside product likes to integrate with Gluster.
>
> On Wed, Nov 25, 2015 at 5:39 PM, Ra
ng GlusterFS is
>> used/tested using fusemount or libgfapi method or both ?
>>
>> On Wed, Nov 25, 2015 at 5:39 PM, Raghavendra Talur
>> wrote:
>>
>>> Hi All,
>>>
>>> Here is a table representing the current state of Gluster testing.
>>>
ou can use this bug https://bugzilla.redhat.com/show_bug.cgi?id=1294826 to
send patches to improve test times.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
proceeding.
We are not yet sure of what could have made the test stay in the same place
for +10 hours before proceeding when a statedump is taken.
Any help here would be appreciated.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel
) bt
#0 0xbb3bb4b7 in ___lwp_park60 () from /usr/lib/libc.so.12
Manu, this seems to be a bug in libperfuse and not in Gluster.
The machine is nbslave75.cloud.gluster.org. You will have to rerun
quota.t couple of times to hit the bug. The test would hang in line 62(TEST
24).
Thanks,
Raghavendra
On Thu, Dec 31, 2015 at 3:24 PM, Emmanuel Dreyfus wrote:
> On Thu, Dec 31, 2015 at 02:51:41PM +0530, Raghavendra Talur wrote:
> > To our surprise though, the hung test started proceeding.
>
> You mean a process gets stuck into a system call for hours and then
> is able to asca
You can log in. I think the HUP signal did not cause any
change in process state. I still see it in I state.
pid is 10967.
On Thu, Dec 31, 2015 at 3:26 PM, Emmanuel Dreyfus wrote:
> On Thu, Dec 31, 2015 at 03:22:54PM +0530, Raghavendra Talur wrote:
> > Manu, this seems to be a bug in l
On Sat, Jan 2, 2016 at 12:03 PM, Atin Mukherjee
wrote:
> -Atin
> Sent from one plus one
>
> On Jan 2, 2016 11:52 AM, "Vijay Bellur" wrote:
> >
> > On 12/30/2015 10:36 AM, Raghavendra Talur wrote:
> >>
> >> This is not comprehensive data but so
On Jan 2, 2016 8:18 PM, "Atin Mukherjee" wrote:
>
> -Atin
> Sent from one plus one
> On Jan 2, 2016 4:41 PM, "Raghavendra Talur" wrote:
> >
> >
> >
> > On Sat, Jan 2, 2016 at 12:03 PM, Atin Mukherjee <
atin.mukherje...@gm
e soon!
Thanks,
Raghavendra Talur
On Tue, Nov 10, 2015 at 11:33 AM, Atin Mukherjee wrote:
> -Atin
> Sent from one plus one
>
> On Nov 10, 2015 11:24 AM, "Kaushal M" wrote:
> >
> > On Tue, Nov 10, 2015 at 9:24 AM, Raghavendra Gowdappa
> > wrote:
> > >
&g
On Fri, Jan 8, 2016 at 12:28 PM, Kaushal M wrote:
> On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M wrote:
> > On Fri, Jan 8, 2016 at 12:03 PM, Raghavendra Talur
> wrote:
> >> Top posting, this is a very old thread.
> >>
> >> Keeping in view the recent
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Jan 12, 2016 2:50 AM, "Niels de Vos" wrote:
>
> On Fri, Jan 08, 2016 at 12:46:09PM +0530, Raghavendra Talur wrote:
> > On Fri, Jan 8, 2016 at 12:28 PM, Kaushal M wrote:
> >
> > > On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M
wrote:
> > > > O
On Jan 12, 2016 3:44 AM, "Michael Adam" wrote:
>
> On 2016-01-08 at 12:03 +0530, Raghavendra Talur wrote:
> > Top posting, this is a very old thread.
> >
> > Keeping in view the recent NetBSD problems and the number of bugs
creeping
> > in, I suggest
hanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
good to
document it.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Wed, Jan 13, 2016 at 2:35 PM, Niels de Vos wrote:
> On Wed, Jan 13, 2016 at 09:56:54AM +0530, Atin Mukherjee wrote:
> > Hi Raghavendra,
> >
> > I noticed that for the below patches Gluster Build system hasn't voted
> > and hence the verified flag doesn't have an ack from it even if the
> > reg
On Wed, Jan 13, 2016 at 4:25 PM, Kaleb Keithley wrote:
> > From: "Niels de Vos"
> >
> > On Wed, Jan 13, 2016 at 09:56:54AM +0530, Atin Mukherjee wrote:
> > > Hi Raghavendra,
> > >
> > > I noticed that for the below patches Gluster Build system hasn't voted
> > > and hence the verified flag doesn
On Thu, Jan 14, 2016 at 10:32 AM, Ravishankar N
wrote:
> On 01/08/2016 12:03 PM, Raghavendra Talur wrote:
>
>> P.S: Stop using the "universal" jenkins account to trigger jenkins build
>> if you are not a maintainer.
>> If you are a maintainer and don't
On Wed, Jan 13, 2016 at 6:32 PM, Niels de Vos wrote:
> On Wed, Jan 13, 2016 at 04:42:12PM +0530, Raghavendra Talur wrote:
> > On Wed, Jan 13, 2016 at 4:25 PM, Kaleb Keithley
> wrote:
> >
> > > > From: "Niels de Vos"
> > > >
> > > >
On Tue, Jan 12, 2016 at 7:59 PM, Atin Mukherjee
wrote:
> -Atin
> Sent from one plus one
> On Jan 12, 2016 7:41 PM, "Niels de Vos" wrote:
> >
> > On Tue, Jan 12, 2016 at 07:21:37PM +0530, Raghavendra Talur wrote:
> > > We have now changed the gerrit-je
Hi Jiffin and Soumya,
Ravishankar told me about core generated by gNFS process
during
./tests/bugs/snapshot/bug-1140162-file-snapshot-features-encrypt-opts-validation.t.
Here is console output:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/17525/console
And here is the backtr
On Sat, Jan 16, 2016 at 2:25 AM, Vijay Bellur wrote:
> On 01/15/2016 08:38 AM, Soumya Koduri wrote:
>
>>
>>
>>
>> On 01/15/2016 06:52 PM, Soumya Koduri wrote:
>>
>>>
>>>
>>> On 01/14/2016 08:41 PM, Vijay Bellur wrote:
>>>
On 01/14/2016 04:11 AM, Jiffin Tony Thottan wrote:
>
>
>>
On Tue, Jan 19, 2016 at 5:20 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
> Result: PASS
> Build timed out (after 300 minutes). Marking the build as failed.
> Build was aborted
> Finished: FAILURE
>
>
> https://build.gluster.org/job/rackspace-regression-2GB-triggered/17664/console
>
>
on, as I used random input numbers, but you
> > get the idea)
> >
> > Two solutions are proposed:
> >
> > 1) do not run unreliable tests, as proposed by Raghavendra Talur:
> > http://review.gluster.org/13173
> >
> > I have nothing against the idea, b
directory looking for strcasecmp(,
). If anything matches then it will return the
. But the problem is the scan is costly. So I wonder if
this is the reason for the CPU spikes.
>
> +Raghavendra Talur, +Poornima
>
> Raghavendra, Poornima,
> When are these getxattrs triggered? D
On Fri, Jan 22, 2016 at 2:41 PM, Michael Scherer
wrote:
> Le vendredi 22 janvier 2016 à 11:31 +0530, Ravishankar N a écrit :
> > On 01/14/2016 12:16 PM, Kaushal M wrote:
> > > On Thu, Jan 14, 2016 at 10:33 AM, Raghavendra Talur
> wrote:
> > >>
> &
add them to developer guide.
Looking forward to be amazed!
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
alstatedir=/var \
--sharedstatedir=/var/lib \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--libdir=/usr/lib64 \
--enable-debug
make install
On Fri, Jan 22, 2016 at 7:43 PM, Raghavendra Talur
wrote:
> HI All,
>
> I am sure there are many tricks hidden under
On Mon, Jan 25, 2016 at 11:29 PM, Michael Scherer
wrote:
> Hi,
>
> so today, after fixing one last config item, the smoke test jobs run
> fine on the Centos 6 builder in the RH DC, which build things as non
> root, then start the tests, then reboot the server.
>
Awesome!
>
> Now, I am looking
comments
above to trigger the job again.
With this we will have time to follow proper process for getting jenkins
account for developers.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo
On Wed, Jan 27, 2016 at 5:34 PM, Niels de Vos wrote:
> Hi all,
>
> yesterday I have posted the latest version of a series that implements
> support for lseek() with SEEK_DATA/SEEK_HOLE. This functionality can
> improve the handling of sparse files immensely.
>
> Please review the changes that inv
On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee
wrote:
> Are we running a different version of run-tests.sh in jenkin slaves. The
> reason of suspection is beacuse in last couple of runs [1] & [2] in
> NetBSD I am seeing no failures apart from bad tests but the regression
> voted failure and I c
date.
On Thu, Jan 28, 2016 at 11:37 AM, Raghavendra Talur
wrote:
>
>
> On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee
> wrote:
>
>> Are we running a different version of run-tests.sh in jenkin slaves. The
>> reason of suspection is beacuse in last couple of runs
On Thu, Jan 28, 2016 at 12:10 PM, Atin Mukherjee
wrote:
>
>
> On 01/28/2016 12:00 PM, Raghavendra Talur wrote:
> > Ok, RCA:
> >
> > In NetBSD cores are being generated in /d/backends/*/*.core
> > run-tests.sh looks only for "/core*" when looking for cor
comment "run-all-regression" or
something like that.
Thoughts?
Thanks
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos wrote:
> On Thu, Feb 04, 2016 at 03:34:05PM +0530, Raghavendra Talur wrote:
> > Hi,
> >
> > We recently changed the jenkins builds to be triggered on the following
> > triggers.
> >
> > 1. Verified+1
> > 2
On Sun, Feb 7, 2016 at 2:51 PM, Nithya Balachandran
wrote:
> Hi,
>
> Can someone please retrigger this regression? It has been aborted in the
> middle of the run.
>
>
Du had re-triggered centos and it is running now.
Netbsd had failed for the same reason.
I have re-triggered.
We are seeing timeo
On Tue, Jan 19, 2016 at 8:33 PM, Emmanuel Dreyfus wrote:
> On Tue, Jan 19, 2016 at 07:08:03PM +0530, Raghavendra Talur wrote:
> > a. Allowing re-running to tests to make them pass leads to complacency
> with
> > how tests are written.
> > b. A test is bad if it is not det
different time
zones.
[1] https://plus.google.com/events/c25hcj9llrvvp3dcidqk26sjrhs
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Tue, Feb 9, 2016 at 9:12 PM, Amye Scavarda wrote:
>
>
> On Tue, Feb 9, 2016 at 3:41 PM, Raghavendra Talur
> wrote:
>
>> Hey folks,
>>
>> Gluster test infrastructure needs a bit of attention. We have committed a
>> lot of code in the last coup
Any comments before I merge the patch http://review.gluster.org/#/c/13393/ ?
On Mon, Feb 8, 2016 at 3:15 PM, Raghavendra Talur wrote:
>
>
> On Tue, Jan 19, 2016 at 8:33 PM, Emmanuel Dreyfus wrote:
>
>> On Tue, Jan 19, 2016 at 07:08:03PM +0530, Raghavendra Talur wrote:
&
*Patches that have passed all tests and are waiting for my review:*
http://review.gluster.org/#/q/status:open+label:CentOS-regression%2B1+AND+label:NetBSD-regression%2B1+AND+label:smoke%2B1+AND+reviewer:self
Thanks,
Raghavendra Talur
___
Gluster-devel mailing
On Fri, Feb 26, 2016 at 7:05 AM, Joseph Fernandes
wrote:
> Hope this helps
>
> Courtesy : Raghvendra Talur (rta...@redhat.com)
>
> 1. Clone glusterfs repo to your laptop and get acquainted with dev
> workflow.
> https://gluster.readthedocs.org/en/latest/Developer-guide/Developers-Index/
>
> 2. If
On Wed, Feb 10, 2016 at 8:29 PM, Emmanuel Dreyfus wrote:
> On Wed, Feb 10, 2016 at 07:30:24PM +0530, Raghavendra Talur wrote:
> > Any comments before I merge the patch
> http://review.gluster.org/#/c/13393/ ?
>
> The proposal has the merit of adressing the multi-OS case, but
On Mar 3, 2016 7:42 AM, "Emmanuel Dreyfus" wrote:
>
> Raghavendra Talur wrote:
>
> > The tests passed on the first run itself, except for the NetBSD with
> > "another test running on slave" error.
>
> Was the previous test on the slave canceled?
Ye
On Thu, Feb 4, 2016 at 7:13 PM, Niels de Vos wrote:
> On Thu, Feb 04, 2016 at 04:15:16PM +0530, Raghavendra Talur wrote:
> > On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos wrote:
> >
> > > On Thu, Feb 04, 2016 at 03:34:05PM +0530, Raghavendra Talur wrote:
> > >
On Fri, Mar 4, 2016 at 6:13 PM, Raghavendra Talur wrote:
>
>
> On Thu, Feb 4, 2016 at 7:13 PM, Niels de Vos wrote:
>
>> On Thu, Feb 04, 2016 at 04:15:16PM +0530, Raghavendra Talur wrote:
>> > On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos wrote:
>> >
>&
On Thu, Mar 3, 2016 at 7:12 AM, Raghavendra Talur wrote:
>
>
> On Wed, Feb 10, 2016 at 8:29 PM, Emmanuel Dreyfus wrote:
>
>> On Wed, Feb 10, 2016 at 07:30:24PM +0530, Raghavendra Talur wrote:
>> > Any comments before I merge the patch
>> http://review.gluster.or
On Mon, Mar 14, 2016 at 8:40 AM, Kaushal M wrote:
> Hey Vijay,
>
> Awesome work on the tests!
>
+1
>
> Could you please list down the tests you run for releases? This would
> help the other release-maintainers could run them as well. We could
> also try automating these tests, so that it beco
rs to trigger build from you.
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
Root cause: I see the following error when I do "test connection"
Connection error : com.jcraft.jsch.JSchException:
java.net.NoRouteToHostException: No route to host
On Wed, Mar 16, 2016 at 10:57 AM, Raghavendra Talur
wrote:
> Hi All,
>
> I see that jenkins isn't g
ility of back porting patches.
Corollary question: Our test-framework is now capable of disabling tests
for certain OS, certain branch etc. I would like to propose that we stop
having tests in main git repo. This will remove need to back port test only
fixes.
Thanks,
Raghavendra
Thanks Kaushal!
On Wed, Mar 16, 2016 at 11:54 AM, Kaushal M wrote:
> Fixed now. Check my reply to Kaleb's earlier mail for the details.
>
> On Wed, Mar 16, 2016 at 11:07 AM, Raghavendra Talur
> wrote:
> > Root cause: I see the following error when I do "test conn
On Wed, Mar 16, 2016 at 11:31 AM, Raghavendra Talur
wrote:
> Hi,
>
> Lot many fixes to tests were found to be not back ported to 3.7 and other
> release branches.
> This causes tests to fail only in those branches and leaves the
> maintainers puzzled.
>
> Also, this s
On Mar 17, 2016 7:50 AM, "Pranith Kumar Karampuri"
wrote:
>
>
>
> On 03/16/2016 11:46 PM, Raghavendra Talur wrote:
>>
>>
>>
>> On Wed, Mar 16, 2016 at 11:39 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>>>
>>>
On Wed, Mar 9, 2016 at 7:39 PM, Kaushal M wrote:
> On Wed, Mar 9, 2016 at 7:02 PM, M S Vishwanath Bhat
> wrote:
> > Hi,
> >
> > When we were discussing about the readiness of distaf for upstream test
> > automation, this question came up, That we should have a process or
> workflow
> > for propo
On Wed, Mar 16, 2016 at 11:59 PM, Atin Mukherjee wrote:
> -Atin
> Sent from one plus one
>
> On 16-Mar-2016 11:32 am, "Raghavendra Talur" wrote:
> >
> > Hi,
> >
> > Lot many fixes to tests were found to be not back ported to 3.7 and
> other rel
On Wed, Mar 16, 2016 at 11:39 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> On 03/16/2016 11:31 AM, Raghavendra Talur wrote:
>
> Hi,
>
> Lot many fixes to tests were found to be not back ported to 3.7 and other
> release branches.
> This c
ing more than one repo) kind of defeats the purpose of
> developers having to concern themselves with only single repo
> (glusterfs.git). Since I couldn't discuss this in weekly gluster meeting in
> #gluster-meeting, let me propose my solution here.
>
This proposal from Jonathan
request infra team to add them
to maintainers group.
[1]: http://review.gluster.org/#/c/13853/
Thanks,
Raghavendra Talur
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Thu, Apr 14, 2016 at 10:13 AM, Atin Mukherjee
wrote:
> I am pretty sure that earlier we used to log the culprit test generating
> the core. But now I don't see that same behavior in these runs [1] [2]
>
> [1]
>
> https://build.gluster.org/job/rackspace-regression-2GB-triggered/19709/consoleFul
/gluster_community_meeting_20-apr-2016.2016-04-20-12.01.txt
- Log:
https://meetbot.fedoraproject.org/gluster-meeting/2016-04-20/gluster_community_meeting_20-apr-2016.2016-04-20-12.01.log.html
Next week's meeting will be held at the same time.
Thanks,
Raghavendra Talur
Meeting su
backport test fixes.
Thanks,
Raghavendra Talur
[1]: http://review.gluster.org/#/c/13683/
[2]:
https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16489/console
[3]:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/20348/console
1 - 100 of 214 matches
Mail list logo
