Re: Regarding a consistent gfapi .t failure

[Poornima Gurusiddaiah <pgurusid@xxxxxxxxxx>]

Oh ok. I see that in ./tests/basic/gfapi/bug1291259.c the function glfs_upcall_get_reason() is causing segmentation fault, as per the stderr messages.

Adding Niels, if he wants to take a look at this.

We can mark the test bad by raising a Bz i suppose.

Thanks,

Poornima

---

From: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
To: "Poornima Gurusiddaiah" <pgurusid@xxxxxxxxxx>
Cc: "Soumya Koduri" <skoduri@xxxxxxxxxx>, "Pranith Karampuri" <pkarampu@xxxxxxxxxx>
Sent: Wednesday, December 14, 2016 1:49:27 AM
Subject: Re: Regarding a consistent gfapi .t failure

No unfortunately I had no success with recreating the failure either on my setup or on a borrowed centos from jenkins cluster.

Ok this is good information. I didn't know it had failed on other patches too. I thought it's only with my patch.

Can this be marked as a bad test in that case?

-Krutika

On Wed, Dec 14, 2016 at 12:08 PM, Poornima Gurusiddaiah <pgurusid@xxxxxxxxxx> wrote:

Hi,

Are you able consistently reproduce this on your local system as well? If so can you share the system?

I see that it has failed for many other patches as well. http://fstat.gluster.org/weeks/1/failure/34

Regards,

Poornima

---

From: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
To: "Poornima Gurusiddaiah" <pgurusid@xxxxxxxxxx>, "Soumya Koduri" <skoduri@xxxxxxxxxx>
Cc: "Pranith Karampuri" <pkarampu@xxxxxxxxxx>
Sent: Tuesday, December 13, 2016 8:47:57 AM
Subject: Regarding a consistent gfapi .t failure

Hi,

The test tests/basic/gfapi/bug1291259.t seems to be failing consistently on my 3.9 backport http://review.gluster.org/#/c/16046/

The patch itself makes changes only in compound fops, so it is unlikely that the failure is caused by the patch itself.

Here's a sample failure run: https://build.gluster.org/job/centos6-regression/2134/console

I ran the test on my laptop and it passes consistently.

I ran the test on a borrowed centos slave and it passes there as well.

I looked at the logfile bug1291259.log from the archived build failure logs

but there are no failures.

If you have any ideas on how to proceed further, could you please suggest the same?

-Krutika

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel