From kiyer at redhat.com Fri Jan 4 12:12:59 2019 From: kiyer at redhat.com (Kshithij Iyer) Date: Fri, 4 Jan 2019 17:42:59 +0530 Subject: [automated-testing] CentOS-CI not pulling latest patches committed to glusto resulting in build failure Message-ID: Hello, I have been trying to verify 2 of my patches through CentOS-CI and have faced issues where CentOS-CI is not being able to fetch the latest patches committed to glusto. The patch went in peer_detach() so all the testcases which use them might fail to verify. Have attached the links to the logs below. Please have a look at it. [ 1 ] https://ci.centos.org/job/gluster_glusto-patch-check/1055/artifact/glustomain.log [ 2 ] https://ci.centos.org/job/gluster_glusto-patch-check/1054/artifact/glustomain.log Thanks, Kshithij Iyer Gluster QE Intern -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigelb at redhat.com Mon Jan 7 03:45:24 2019 From: nigelb at redhat.com (Nigel Babu) Date: Mon, 7 Jan 2019 09:15:24 +0530 Subject: [automated-testing] CentOS-CI not pulling latest patches committed to glusto resulting in build failure In-Reply-To: References: Message-ID: Hi Kshithij, Let me restate the problem. Please correct me if I'm wrong. You have two patches[1], [2] that are not passing Centos CI at the moment. Both your patches are failing because you do not have Nag's fixes for peer detach[3]. It's not the CI's job to rebase your patch. You have to rebase your patch. You can either do that manually with the git cli or you can use the rebase button on Gerrit. To verify it has worked correctly, after you rebase, look for the "Parent(s)" line on Gerrit, click on "(cgit)" after the commit hash, which will take you to the parent for your change. Make sure your parent is newer than Nag's fix. Then retrigger Centos-CI and it should run with your fixes. This is a mailing list. Please subscribe to the list on lists.gluster.org before sending an email or you will be stuck in moderation. [1]: https://review.gluster.org/#/c/glusto-tests/+/21862/ [2]: https://review.gluster.org/#/c/glusto-tests/+/21932/ [3]: https://review.gluster.org/#/c/glusto-tests/+/21983/ On Mon, Jan 7, 2019 at 8:54 AM Kshithij Iyer wrote: > Hello, > I have been trying to verify 2 of my patches through CentOS-CI and have > faced issues where CentOS-CI is not being able to fetch the latest patches > committed to glusto. The patch went in peer_detach() so all the testcases > which use them might fail to verify. Have attached the links to the logs > below. Please have a look at it. > > [ 1 ] > https://ci.centos.org/job/gluster_glusto-patch-check/1055/artifact/glustomain.log > [ 2 ] > https://ci.centos.org/job/gluster_glusto-patch-check/1054/artifact/glustomain.log > > Thanks, > Kshithij Iyer > Gluster QE Intern > > > _______________________________________________ > automated-testing mailing list > automated-testing at gluster.org > https://lists.gluster.org/mailman/listinfo/automated-testing > -- nigelb -------------- next part -------------- An HTML attachment was scrubbed... URL: From kiyer at redhat.com Mon Jan 7 14:46:10 2019 From: kiyer at redhat.com (Kshithij Iyer) Date: Mon, 7 Jan 2019 20:16:10 +0530 Subject: [automated-testing] CentOS-CI not pulling latest patches committed to glusto resulting in build failure In-Reply-To: References: Message-ID: Hi Nigel, Thank you for the advise. However I have observed that there is one other issue with CentOS-CI or the Jenkins job(Not sure of what is wrong!), the domain names are not properly configured which leads to [1]. '*hostname -s*' is the command which is used to fetch network short names, however while running it on CentOS-CI it returns only *n16* instead of returning *n16.dusty. *This happens because *`hostname -s`* splits the hostname till the first *. (dot) *due to which it only returns a part of the actual network short name which causes the peer probe to fail with "*peer probe: failed: Probe returned with Transport endpoint is not connected" *error*.* The solution to this problem could be to configure the domain name such that *`hostname -s` *returns *n16-dusty *instead of *n16.dusty *by replacing the *.(dot) *with a *-(dash). *[1]: https://ci.centos.org/job/gluster_glusto-patch-check/1058/artifact/glustomain.log Thanks, Kshithij Iyer Gluster QE Intern On Mon, Jan 7, 2019 at 9:16 AM Nigel Babu wrote: > Hi Kshithij, > > Let me restate the problem. Please correct me if I'm wrong. You have two > patches[1], [2] that are not passing Centos CI at the moment. Both your > patches are failing because you do not have Nag's fixes for peer detach[3]. > It's not the CI's job to rebase your patch. You have to rebase your patch. > You can either do that manually with the git cli or you can use the rebase > button on Gerrit. > > To verify it has worked correctly, after you rebase, look for the > "Parent(s)" line on Gerrit, click on "(cgit)" after the commit hash, which > will take you to the parent for your change. Make sure your parent is newer > than Nag's fix. Then retrigger Centos-CI and it should run with your fixes. > > This is a mailing list. Please subscribe to the list on lists.gluster.org > before sending an email or you will be stuck in moderation. > > [1]: https://review.gluster.org/#/c/glusto-tests/+/21862/ > [2]: https://review.gluster.org/#/c/glusto-tests/+/21932/ > [3]: https://review.gluster.org/#/c/glusto-tests/+/21983/ > > On Mon, Jan 7, 2019 at 8:54 AM Kshithij Iyer wrote: > >> Hello, >> I have been trying to verify 2 of my patches through CentOS-CI and have >> faced issues where CentOS-CI is not being able to fetch the latest patches >> committed to glusto. The patch went in peer_detach() so all the testcases >> which use them might fail to verify. Have attached the links to the logs >> below. Please have a look at it. >> >> [ 1 ] >> https://ci.centos.org/job/gluster_glusto-patch-check/1055/artifact/glustomain.log >> [ 2 ] >> https://ci.centos.org/job/gluster_glusto-patch-check/1054/artifact/glustomain.log >> >> Thanks, >> Kshithij Iyer >> Gluster QE Intern >> >> >> _______________________________________________ >> automated-testing mailing list >> automated-testing at gluster.org >> https://lists.gluster.org/mailman/listinfo/automated-testing >> > > > -- > nigelb > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigelb at redhat.com Tue Jan 8 09:13:32 2019 From: nigelb at redhat.com (Nigel Babu) Date: Tue, 8 Jan 2019 14:43:32 +0530 Subject: [automated-testing] CentOS-CI not pulling latest patches committed to glusto resulting in build failure In-Reply-To: References: Message-ID: Hi Kshithij, This is not an environment where we can control such variables, unfortunately. We have to work with what we have. The environment gets wiped every time. Even with your solution, I doubt it helps, because it will still need an /etc/hosts entry. At which point whether there's a hyphen or no hyphen doesn't matter. We could add what we wanted. On Mon, Jan 7, 2019 at 8:16 PM Kshithij Iyer wrote: > Hi Nigel, > Thank you for the advise. > However I have observed that there is one other issue with CentOS-CI or > the Jenkins job(Not sure of what is wrong!), the domain names are not > properly configured which leads to [1]. '*hostname -s*' is the command > which is used to fetch network short names, however while running it on > CentOS-CI it returns only *n16* instead of returning *n16.dusty. *This > happens because *`hostname -s`* splits the hostname till the first *. > (dot) *due to which it only returns a part of the actual network short > name which causes the peer probe to fail with "*peer probe: failed: Probe > returned with Transport endpoint is not connected" *error*.* The solution > to this problem could be to configure the domain name such that *`hostname > -s` *returns *n16-dusty *instead of *n16.dusty *by replacing the *.(dot) *with > a > > *-(dash). *[1]: > https://ci.centos.org/job/gluster_glusto-patch-check/1058/artifact/glustomain.log > > Thanks, > Kshithij Iyer > Gluster QE Intern > > > > > On Mon, Jan 7, 2019 at 9:16 AM Nigel Babu wrote: > >> Hi Kshithij, >> >> Let me restate the problem. Please correct me if I'm wrong. You have two >> patches[1], [2] that are not passing Centos CI at the moment. Both your >> patches are failing because you do not have Nag's fixes for peer detach[3]. >> It's not the CI's job to rebase your patch. You have to rebase your patch. >> You can either do that manually with the git cli or you can use the rebase >> button on Gerrit. >> >> To verify it has worked correctly, after you rebase, look for the >> "Parent(s)" line on Gerrit, click on "(cgit)" after the commit hash, which >> will take you to the parent for your change. Make sure your parent is newer >> than Nag's fix. Then retrigger Centos-CI and it should run with your fixes. >> >> This is a mailing list. Please subscribe to the list on lists.gluster.org >> before sending an email or you will be stuck in moderation. >> >> [1]: https://review.gluster.org/#/c/glusto-tests/+/21862/ >> [2]: https://review.gluster.org/#/c/glusto-tests/+/21932/ >> [3]: https://review.gluster.org/#/c/glusto-tests/+/21983/ >> >> On Mon, Jan 7, 2019 at 8:54 AM Kshithij Iyer wrote: >> >>> Hello, >>> I have been trying to verify 2 of my patches through CentOS-CI and have >>> faced issues where CentOS-CI is not being able to fetch the latest patches >>> committed to glusto. The patch went in peer_detach() so all the testcases >>> which use them might fail to verify. Have attached the links to the logs >>> below. Please have a look at it. >>> >>> [ 1 ] >>> https://ci.centos.org/job/gluster_glusto-patch-check/1055/artifact/glustomain.log >>> [ 2 ] >>> https://ci.centos.org/job/gluster_glusto-patch-check/1054/artifact/glustomain.log >>> >>> Thanks, >>> Kshithij Iyer >>> Gluster QE Intern >>> >>> >>> _______________________________________________ >>> automated-testing mailing list >>> automated-testing at gluster.org >>> https://lists.gluster.org/mailman/listinfo/automated-testing >>> >> >> >> -- >> nigelb >> > -- nigelb -------------- next part -------------- An HTML attachment was scrubbed... URL: From kiyer at redhat.com Wed Jan 9 10:35:03 2019 From: kiyer at redhat.com (Kshithij Iyer) Date: Wed, 9 Jan 2019 16:05:03 +0530 Subject: [automated-testing] CentOS-CI fails with keypair error. Message-ID: Hello, While attempting to review my patches through CentOS-CI, it was observed that CentOS-CI was hitting keypair error. This occurred as soon as I started the test run. The logs are attached below: [1] https://ci.centos.org/job/gluster_glusto-patch-check/1062/console [2] https://ci.centos.org/job/gluster_glusto-patch-check/1063/console Thanks, Kshithij Iyer Gluster QE Intern -------------- next part -------------- An HTML attachment was scrubbed... URL: From vkoriako at redhat.com Fri Jan 25 14:16:27 2019 From: vkoriako at redhat.com (Vitalii Koriakov) Date: Fri, 25 Jan 2019 09:16:27 -0500 (EST) Subject: [automated-testing] Jankins fails In-Reply-To: <1367410483.98704142.1548425750482.JavaMail.zimbra@redhat.com> Message-ID: <242013690.98704179.1548425786995.JavaMail.zimbra@redhat.com> Hallo all. It seems something is broken on Jenkins. It fails with a bit amount of pylint errors https://build.gluster.org/job/glusto-tests-lint/3307/console Regards, Vitalii From vavuthu at redhat.com Fri Jan 25 15:39:59 2019 From: vavuthu at redhat.com (Vijay Bhaskar Reddy Avuthu) Date: Fri, 25 Jan 2019 21:09:59 +0530 Subject: [automated-testing] Jankins fails In-Reply-To: <242013690.98704179.1548425786995.JavaMail.zimbra@redhat.com> References: <1367410483.98704142.1548425750482.JavaMail.zimbra@redhat.com> <242013690.98704179.1548425786995.JavaMail.zimbra@redhat.com> Message-ID: HI Vitalii, I have done recheck and looks fine now. https://build.gluster.org/job/glusto-tests-lint/3308/ Regards, Vijay A On Fri, Jan 25, 2019 at 7:55 PM Vitalii Koriakov wrote: > Hallo all. > > It seems something is broken on Jenkins. It fails with a bit amount of > pylint errors > https://build.gluster.org/job/glusto-tests-lint/3307/console > > Regards, Vitalii > _______________________________________________ > automated-testing mailing list > automated-testing at gluster.org > https://lists.gluster.org/mailman/listinfo/automated-testing > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vkoriako at redhat.com Mon Jan 28 08:57:40 2019 From: vkoriako at redhat.com (Vitalii Koriakov) Date: Mon, 28 Jan 2019 03:57:40 -0500 (EST) Subject: [automated-testing] Jankins fails In-Reply-To: References: <1367410483.98704142.1548425750482.JavaMail.zimbra@redhat.com> <242013690.98704179.1548425786995.JavaMail.zimbra@redhat.com> Message-ID: <1512721505.98997186.1548665860547.JavaMail.zimbra@redhat.com> Thanks, but it weird... I started it twice. Regards, Vitalii ----- ???????? ????????? ----- ??: "Vijay Bhaskar Reddy Avuthu" ????: "Vitalii Koriakov" ?????: automated-testing at gluster.org ????????????: ???????, 25 ?????? 2019 ? 17:39:59 ????: Re: [automated-testing] Jankins fails HI Vitalii, I have done recheck and looks fine now. https://build.gluster.org/job/glusto-tests-lint/3308/ Regards, Vijay A On Fri, Jan 25, 2019 at 7:55 PM Vitalii Koriakov wrote: > Hallo all. > > It seems something is broken on Jenkins. It fails with a bit amount of > pylint errors > https://build.gluster.org/job/glusto-tests-lint/3307/console > > Regards, Vitalii > _______________________________________________ > automated-testing mailing list > automated-testing at gluster.org > https://lists.gluster.org/mailman/listinfo/automated-testing >