[Gluster-devel] Rackspace regression slaves hung?
Hi Justin, It looks like slaves 22-25 are hung for over 23 hours now? -Krutika ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Weekly GlusterFS Community Meeting results
Meeting Minutes: http://meetbot.fedoraproject.org/gluster-meeting/2014-08-27/gluster-meeting.2014-08-27-12.04.html Full Log: http://meetbot.fedoraproject.org/gluster-meeting/2014-08-27/gluster-meeting.2014-08-27-12.04.log.html -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
> Currently we name tests associated with a bug with just the bug-id as > 'bug-XXX.t'. This naming doesn't provide any context directly, and > someone looking at just the name wouldn't know what it does. > > I suggest that we use slightly more descriptive names to the tests. > Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. > This provides just enough context to understand what the test is > trying to do from just the name. > > How do you all feel about this? It's an excellent idea. While we're at it, it would also be nice if tests were arranged into subdirectories so that it's easier to find those that might be particularly useful for testing new code. BTW, it should be possible to write a script that would fetch the bug title from Bugzilla, which (properly mangled) could be a first guess at the new test name. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Need a couple of reviews for http://review.gluster.org/8346
Thank you in advance. Regards, Santosh ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] glfs_creat this method hang up
Could you please share your glusterfs_example code and the steps you have used to compile it and execute the binary? Would like to check how the gfapi header files are linked. Thanks, Soumya On 08/27/2014 03:22 PM, Pranith Kumar Karampuri wrote: Guys who work with glfs_*, could you guys reply to this question. Pranith On 08/27/2014 03:16 PM, ABC-new wrote: hi~: while i run the glusterfs example via libgfapi, gcc -c glusterfs_example -o glfs -luuid the method glfs_creat hang up. I want to generate the uuid for file name. thank you. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
On 08/27/2014 03:29 PM, Lalatendu Mohanty wrote: On 08/27/2014 02:13 PM, Niels de Vos wrote: On Wed, Aug 27, 2014 at 01:50:40PM +0530, Kaushal M wrote: I'll do that, if someone could point me to it. Is it on the community wiki or in doc/ directory in the source? Seems to be only (?) on the wiki: - http://www.gluster.org/community/documentation/index.php/Using_the_Gluster_Test_Framework#Creating_your_own_tests Niels We should also update README.md file in source code i.e. glusterfs/tests. + Forgot to add that README.md does not a section about writing tests, either we add a new section or we can update the wiki page and update the wiki link in the README file. -Lala ~kaushal On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos wrote: On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote: Hi all, Currently we name tests associated with a bug with just the bug-id as 'bug-XXX.t'. This naming doesn't provide any context directly, and someone looking at just the name wouldn't know what it does. I suggest that we use slightly more descriptive names to the tests. Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. This provides just enough context to understand what the test is trying to do from just the name. How do you all feel about this? Sounds good to me. Please make sure to update the documentation about writing test-cases in a few days, if nobody objects. Thanks, Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
On 08/27/2014 02:13 PM, Niels de Vos wrote: On Wed, Aug 27, 2014 at 01:50:40PM +0530, Kaushal M wrote: I'll do that, if someone could point me to it. Is it on the community wiki or in doc/ directory in the source? Seems to be only (?) on the wiki: - http://www.gluster.org/community/documentation/index.php/Using_the_Gluster_Test_Framework#Creating_your_own_tests Niels We should also update README.md file in source code i.e. glusterfs/tests. -Lala ~kaushal On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos wrote: On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote: Hi all, Currently we name tests associated with a bug with just the bug-id as 'bug-XXX.t'. This naming doesn't provide any context directly, and someone looking at just the name wouldn't know what it does. I suggest that we use slightly more descriptive names to the tests. Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. This provides just enough context to understand what the test is trying to do from just the name. How do you all feel about this? Sounds good to me. Please make sure to update the documentation about writing test-cases in a few days, if nobody objects. Thanks, Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] glfs_creat this method hang up
Guys who work with glfs_*, could you guys reply to this question. Pranith On 08/27/2014 03:16 PM, ABC-new wrote: hi~: while i run the glusterfs example via libgfapi, gcc -c glusterfs_example -o glfs -luuid the method glfs_creat hang up. I want to generate the uuid for file name. thank you. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
On Wed, Aug 27, 2014 at 01:50:40PM +0530, Kaushal M wrote: > I'll do that, if someone could point me to it. Is it on the community > wiki or in doc/ directory in the source? Seems to be only (?) on the wiki: - http://www.gluster.org/community/documentation/index.php/Using_the_Gluster_Test_Framework#Creating_your_own_tests Niels > > ~kaushal > > On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos wrote: > > On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote: > >> Hi all, > >> > >> Currently we name tests associated with a bug with just the bug-id as > >> 'bug-XXX.t'. This naming doesn't provide any context directly, and > >> someone looking at just the name wouldn't know what it does. > >> > >> I suggest that we use slightly more descriptive names to the tests. > >> Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. > >> This provides just enough context to understand what the test is > >> trying to do from just the name. > >> > >> How do you all feel about this? > > > > Sounds good to me. Please make sure to update the documentation about > > writing test-cases in a few days, if nobody objects. > > > > Thanks, > > Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
I'll do that, if someone could point me to it. Is it on the community wiki or in doc/ directory in the source? ~kaushal On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos wrote: > On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote: >> Hi all, >> >> Currently we name tests associated with a bug with just the bug-id as >> 'bug-XXX.t'. This naming doesn't provide any context directly, and >> someone looking at just the name wouldn't know what it does. >> >> I suggest that we use slightly more descriptive names to the tests. >> Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. >> This provides just enough context to understand what the test is >> trying to do from just the name. >> >> How do you all feel about this? > > Sounds good to me. Please make sure to update the documentation about > writing test-cases in a few days, if nobody objects. > > Thanks, > Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote: > Hi all, > > Currently we name tests associated with a bug with just the bug-id as > 'bug-XXX.t'. This naming doesn't provide any context directly, and > someone looking at just the name wouldn't know what it does. > > I suggest that we use slightly more descriptive names to the tests. > Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. > This provides just enough context to understand what the test is > trying to do from just the name. > > How do you all feel about this? Sounds good to me. Please make sure to update the documentation about writing test-cases in a few days, if nobody objects. Thanks, Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] A suggestion on naming test files.
On 27/08/2014, at 7:56 AM, Pranith Kumar Karampuri wrote: > On 08/27/2014 12:21 PM, Kaushal M wrote: >> Hi all, >> >> Currently we name tests associated with a bug with just the bug-id as >> 'bug-XXX.t'. This naming doesn't provide any context directly, and >> someone looking at just the name wouldn't know what it does. >> >> I suggest that we use slightly more descriptive names to the tests. >> Lets name the tests as 'bug-XXX-checking-if-feature-Y-works.t'. >> This provides just enough context to understand what the test is >> trying to do from just the name. >> >> How do you all feel about this? > +100 Yeah, this sounds like a good idea. If I ever get around to writing test cases :>, I'll try that out. ;) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
