Hello, This job is now green. The primary problem here had to do with the community cage's networking. I raised the issue to the cage team and the Centos CI folks yesterday. They've resolved it now. The root cause was a problem with the MTU. We have a temporary fix at the Centos Gateway. Once the network team is freed up, they'll fix it permanently. On Wed, Nov 02, 2016 at 05:02:07AM -0400, Prashanth Pai wrote: > > ----- Original Message ----- > > From: "Nigel Babu" <nigelb@xxxxxxxxxx> > > To: "Prashanth Pai" <ppai@xxxxxxxxxx> > > Cc: "Niels de Vos" <ndevos@xxxxxxxxxx>, gluster-devel@xxxxxxxxxxx > > Sent: Wednesday, 2 November, 2016 1:17:14 PM > > Subject: Re: CentOS CI failing for libgfapi-python tests > > > > Hi Prashanth, > > > > The last we talked about this failure, you mentioned you couldn't reproduce > > the > > failure on your VM. Were you finally able to reproduce the failure? > > No. I couldn't. > > > > > If the tests are passing on the VM without being able to reproduce the > > failure > > on the same VM, that doesn't give us any useful information. > > Right. > The only way to be sure is to re-enable the tests to run on CentOS CI. > I vaguely recall you mentioning that you could hit the issue on > your machine. Could you give it a run on latest glusterfs bits ? > > > > > Niels, I rebuild the jobs manually. I intend to automate it eventually, but > > for > > now, it remains a task to be done after merging any changes to the JJB > > files/scripts. > > > > On Wed, Nov 02, 2016 at 03:28:27AM -0400, Prashanth Pai wrote: > > > Thanks Niels. > > > > > > I ran the libgfapi-python tests on glusterfs source's master > > > branch, which includes http://review.gluster.org/15620 and > > > I see all tests passing on my test VM. > > > > > > -Prashanth Pai > > > -- nigelb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
