[Gluster-devel] How should I submit a testcase without proper solution

[Anders Blomdell]

Hi,

finally got around to look into Symlink mtime changes when rebalancing
(https://bugzilla.redhat.com/show_bug.cgi?id=1122443), and I have submitted a 
test-case (http://review.gluster.org/#/c/8383/), but that is expected to 
fail (since I have not managed to write a patch that adresses the problem), 
and hence it will be voted down by Jenkins, is there something I should do
about this?

/Anders 

-- 
Anders Blomdell  Email: anders.blomd...@control.lth.se
Department of Automatic Control
Lund University  Phone:+46 46 222 4625
P.O. Box 118 Fax:  +46 46 138118
SE-221 00 Lund, Sweden

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] How should I submit a testcase without proper solution

[Pranith Kumar Karampuri]

hi Anders,
   Generally new test cases are submitted along with the fix to prevent 
this situation. You should either submit the fix along with the test 
case or wait until the fix is submitted by someone else in case you are 
not actively working on it and then we can re-trigger the regression 
build for this patch. Then it will be taken in.


Pranith
On 07/29/2014 08:51 PM, Anders Blomdell wrote:

Hi,

finally got around to look into Symlink mtime changes when rebalancing
(https://bugzilla.redhat.com/show_bug.cgi?id=1122443), and I have submitted a
test-case (http://review.gluster.org/#/c/8383/), but that is expected to
fail (since I have not managed to write a patch that adresses the problem),
and hence it will be voted down by Jenkins, is there something I should do
about this?

/Anders



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel