Can this patch be reverted asap as it has blocked other patches to get in? IMO, we shouldn't be marking the test as bad given we know the patch which introduced the regression.
On Tue, Feb 28, 2017 at 4:16 PM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
https://review.gluster.org/16462 has caused this regression as per the git bisect.On Tue, Feb 28, 2017 at 3:28 PM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:This is being tracked @ https://bugzilla.redhat.com/show_bug.cgi?id=1427404 , krutika posted a patch to move it to bad tests until we find why a lookup on one file is leading to lookup on the hardlink instead.--On Tue, Feb 28, 2017 at 2:56 PM, Susant Palai <spalai@xxxxxxxxxx> wrote:Hi,
test case: ./tests/bitrot/bug-1373520.t is seen to be failing on different regression runs on master.
Requesting to look in to it.
Few instances:
https://build.gluster.org/job/netbsd7-regression/3118/consol eFull
https://build.gluster.org/job/centos6-regression/3451/
https://build.gluster.org/job/netbsd7-regression/3122/consol eFull
Thanks,
Susant
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
Pranith
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
--~ Atin (atinm)
--
~ Atin (atinm)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
