As per Jeff's comment on getting the component from bugzilla,
this command works:
[rtalur@rastarpad bugs]$ find . -name "*.t" | \grep -o "[0-9]\+" | tr "\n"
" " |xargs -n 1 bugzilla query --outputformat '%{bug_id}: %{component}'
--bug_id
974007: glusterd
1101647: replicate
1112613: glusterd
95787
And while we're at it, may we please rename the two or three test files
that don't start with bug- to be (foolishly) consistent with the rest of
our tests?
Feeling more ambitious? How about renaming all the bug-$sixdigit.t to
bug-0$sixdigit.t for some even more foolish consistency. (That's a z
> Jeff, Could you explain what you meant by 'arranged into
> subdirectories'? I didn't understand what you meant by that.
I think it would be great if we had an "afr" directory and an "nfs"
directory and a "glusterd" directory for bugs related to AFR, NFS, or
glusterd respectively - and likewise f
All,
Since I've had no objections to this idea, I'm going to update the
documentation with this.
Jeff, Could you explain what you meant by 'arranged into
subdirectories'? I didn't understand what you meant by that.
~kaushal
On Wed, Aug 27, 2014 at 5:07 PM, Jeff Darcy wrote:
>> Currently we name
> 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 te
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 wik
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/documentati
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_Framewo
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
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
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
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 descrip
12 matches
Mail list logo
