Re: [Gluster-devel] regarding spurious failure tests/bugs/bug-1112559.t

2014-07-14 Thread Joseph Fernandes
Hi All, Thanks Justin for the setup(slave30). Executed the whole regression suite on slave30 multiple times. Once there was a failure of ./tests/basic/mgmt_v3-locks.t with a core http://build.gluster.org/job/rackspace-regression-2GB-joe/12/console Test Summary Report ---

Re: [Gluster-devel] P

2014-07-14 Thread Emmanuel Dreyfus
Raghavendra Gowdappa rgowd...@redhat.com wrote: I can help you out with the review of the paper. Here is it, please send a diff with your changes: http://ftp.espci.fr/shadow/manu/fuse.txt -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org

[Gluster-devel] Proposal for change regarding latency calculation

2014-07-14 Thread Vipul Nayyar
Hello, Following is a proposal for modifying the io profiling capability of the io-stats xlator. I recently sent in a patch(review.gluster.org/#/c/8244/) regarding that, which uses the already written latency related functions in io-stats to dump info through meta and added some more data

Re: [Gluster-devel] Is this a transient failure?

2014-07-14 Thread Justin Clift
On 14/07/2014, at 6:38 AM, Pranith Kumar Karampuri wrote: snip Kick off a regression test manually here, and see if the same failure occurs: http://build.gluster.org/job/rackspace-regression-2GB/ If it happens again, it's not a spurious one. I believe this is a spurious one. I didn't

Re: [Gluster-devel] regarding spurious failure tests/bugs/bug-1112559.t

2014-07-14 Thread Justin Clift
On 14/07/2014, at 7:40 AM, Joseph Fernandes wrote: snip After this I restart slave30 and executed the whole regression test again and never hit his issue. Looks like the issue is not originated @ bug-1112559.t. The failure in bug-1112559.t test 10 is the result because of a previous

[Gluster-devel] Updating blog entry list on www.gluster.org?

2014-07-14 Thread Justin Clift
Hi Eco, Humble just published a blog post about the new GlusterFS 3.4.5 beta2 RPMs: http://blog.gluster.org/2014/07/glusterfs-3-4-5beta2-rpms-are-available-now/ How do we get the www.gluster.org website updated, so new blog posts appear automagically? Regards and best wishes, Justin Clift

Re: [Gluster-devel] Patches to be merged before 3.6 branching

2014-07-14 Thread Kaushal M
My patch for improving peer identification [1] needs to get in. It's functionally complete and can be merged right now. But KP has some minor comments. I'll update it tonight, and it should be good for merge by the morning, ~kaushal [1] https://review.gluster.org/8238 On Mon, Jul 14, 2014 at

Re: [Gluster-devel] Patches to be merged before 3.6 branching

2014-07-14 Thread Anders Blomdell
On 2014-07-14 16:03, Vijay Bellur wrote: Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update this thread. Does this mean that

[Gluster-devel] Is it OK to pick Code-Reviewer(s)

2014-07-14 Thread Anders Blomdell
When submitting patches where there is an/some obvious person(s) to blame, is it OK/desirable to request them as Code-Reviewers in gerrit? /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:

Re: [Gluster-devel] Is it OK to pick Code-Reviewer(s)

2014-07-14 Thread Jeff Darcy
When submitting patches where there is an/some obvious person(s) to blame, is it OK/desirable to request them as Code-Reviewers in gerrit? Inviting reviewers with clear interest or knowledge in a piece of code is not only OK but recommended. I think blame might not be a good idea, though.

Re: [Gluster-devel] Is it OK to pick Code-Reviewer(s)

2014-07-14 Thread Harshavardhana
On Mon, Jul 14, 2014 at 9:31 AM, Anders Blomdell anders.blomd...@control.lth.se wrote: When submitting patches where there is an/some obvious person(s) to blame, is it OK/desirable to request them as Code-Reviewers in gerrit? Gist of adding Core-Reviewers is to find faults in oneself - not the

Re: [Gluster-devel] Patches to be merged before 3.6 branching

2014-07-14 Thread Justin Clift
On 14/07/2014, at 4:20 PM, Anders Blomdell wrote: On 2014-07-14 16:03, Vijay Bellur wrote: Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update

Re: [Gluster-devel] Change in glusterfs[master]: porting: use __builtin_ffsll() instead of ffsll()

2014-07-14 Thread Pranith Kumar Karampuri
CC gluster-devel, Anuradha who committed the test. Pranith On 07/15/2014 01:58 AM, Harshavardhana wrote: Mr Spurious is here again! Patch Set 2: Verified-1 http://build.gluster.org/job/rackspace-regression-2GB-triggered/351/consoleFull : FAILED Test Summary Report ---

Re: [Gluster-devel] Paper about GlusterFS on NetBSD

2014-07-14 Thread Emmanuel Dreyfus
Raghavendra Gowdappa rgowd...@redhat.com wrote: What is the time-line you want this to be reviewed within? I am busy this week. Is it ok if I can pick this up after this week? If it is very urgent I can try to allocate some time for it. Next week is fine, no problem. -- Emmanuel Dreyfus

[Gluster-devel] Change DEFAULT_WORKDIR from hard-coded value

2014-07-14 Thread Harshavardhana
http://review.gluster.org/#/c/8246/ Two important things it achieves - Break-way from '/var/lib/glusterd' hard-coded previously, instead rely on 'configure' value from 'localstatedir' - Provide 's/lib/db' as default working directory for gluster management daemon for BSD and Darwin based