Jenkins build failure due to "publish of test report" failing
Hi Infra team, I am getting jenkins build failures for my patches, but it does not seem related to the change I made Pls see the chat I had with ewoud below. Let me know whether I need to re-post my patches ? thanx, deepak <deepakcs> is anybody seeing jenkins unit test failures ? I am getting some @ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/31/console <deepakcs> but they don't seem to be related to my patch changes at all <deepakcs> and the unit tests ran fine on my devpt system ! <deepakcs> fsimonce, ^^ can u provide some insight ? * acathrow (~acathrow@pool-173-76-239-245.bstnma.fios.verizon.net) has left #vdsm <ewoud> deepakcs: maybe the EL job is configgured different from th fedora one? <deepakcs> ewoud, you mean if it had run on fedora, it would have possible passed the test ? <ewoud> deepakcs: if you look at the console output you can see EL tries to publish unit test results where fedora doesn't <ewoud> Build step 'Publish JUnit test result report' changed build result to FAILURE <deepakcs> ewoud, i see some ERROR in untitests too .. related to eth0 / net tests.. which i don't see on my fedora devpt box <deepakcs> ewoud, so whats the next step for me ? resubit and hope that it runs on fedora ? <ewoud> deepakcs: no, it's configured to always run on both <ewoud> current step would be to find a jenkins job admin who can change it <deepakcs> ewoud, not clear to me. the publishing of test is failing, hence the overall build is failing, so someone needs to fix that ? <ewoud> deepakcs: yes, it's misconfigured on EL <ewoud> deepakcs: http://www.ovirt.org/Infrastructure_team_assignments tells me eedri and dcaro are general jenkins admins, but maybe someone in the VDSM team can also configure it <deepakcs> ewoud, wondering why i don't see build failure mails for other patches on the list ? <ewoud> deepakcs: that I don't know <deepakcs> ewoud, any idea abt some of the ERROR seen by the unit tests in that console o/p ? <ewoud> deepakcs: I also think that there should be one job to build vdsm and have it in a grid config so it builds on multiple platforms, but I'll poke eedri/dcaro about it <deepakcs> ewoud, thanks, so I won't repost my patches then <ewoud> deepakcs: that looks odd because first it shows an error and then OK <apuimedo> ewoud, deepakcs it is because of el having Python 2.6 instead of 2.7 <ewoud> apuimedo: yes, but then I'd expect it to just show an error and not OK <deepakcs> ewoud, apuimedo thanks. I didn't notice the OK embedded after the error :) <apuimedo> ewoud, yeah... I guess the jenkins job could be better done :P <apuimedo> deepakcs, hopefully today it'll be fixed <apuimedo> by a patch from saggi <ewoud> deepakcs: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/ only shows errors so you're not alone <deepakcs> ewoud, some consolation for me :) <ewoud> deepakcs: I poked dcaro on #vdsm (OFTC) <deepakcs> you mean #ovirt ? <ewoud> euh yes <ewoud> but it can't hurt to send an email to infra@ovirt.org and/or create a ticket in trac <deepakcs> i hope the 'X' against my verified goes away ;) <deepakcs> ewoud, I can do that and paste this chatlog of ours <deepakcs> i mean send mail to the infra team <ewoud> I don't think there's a way to rerun the unit tests unless you push a new set, but there's no point until the job is fixed <deepakcs> ewoud, i thot if they fixed the issue, they will have the test re-run on all the failed patches ? <ewoud> deepakcs: not sure because gerrit triggers a build and not sure if you can easily trigger it again <deepakcs> ok
On Thu 24 Jan 2013 04:40:47 PM IST, Deepak C Shetty wrote:
Hi Infra team, I am getting jenkins build failures for my patches, but it does not seem related to the change I made Pls see the chat I had with ewoud below.
Let me know whether I need to re-post my patches ?
That problem seems to be older than your patch, it's related to the generation of the nose reports, someone from vdsm should take a deeper look into it (in cc). No need to repost, I can rerun the job manually if needed.
thanx, deepak
<deepakcs> is anybody seeing jenkins unit test failures ? I am getting some @ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/31/console <deepakcs> but they don't seem to be related to my patch changes at all <deepakcs> and the unit tests ran fine on my devpt system ! <deepakcs> fsimonce, ^^ can u provide some insight ? * acathrow (~acathrow@pool-173-76-239-245.bstnma.fios.verizon.net) has left #vdsm <ewoud> deepakcs: maybe the EL job is configgured different from th fedora one? <deepakcs> ewoud, you mean if it had run on fedora, it would have possible passed the test ? <ewoud> deepakcs: if you look at the console output you can see EL tries to publish unit test results where fedora doesn't <ewoud> Build step 'Publish JUnit test result report' changed build result to FAILURE <deepakcs> ewoud, i see some ERROR in untitests too .. related to eth0 / net tests.. which i don't see on my fedora devpt box <deepakcs> ewoud, so whats the next step for me ? resubit and hope that it runs on fedora ? <ewoud> deepakcs: no, it's configured to always run on both <ewoud> current step would be to find a jenkins job admin who can change it <deepakcs> ewoud, not clear to me. the publishing of test is failing, hence the overall build is failing, so someone needs to fix that ? <ewoud> deepakcs: yes, it's misconfigured on EL <ewoud> deepakcs: http://www.ovirt.org/Infrastructure_team_assignments tells me eedri and dcaro are general jenkins admins, but maybe someone in the VDSM team can also configure it <deepakcs> ewoud, wondering why i don't see build failure mails for other patches on the list ? <ewoud> deepakcs: that I don't know <deepakcs> ewoud, any idea abt some of the ERROR seen by the unit tests in that console o/p ? <ewoud> deepakcs: I also think that there should be one job to build vdsm and have it in a grid config so it builds on multiple platforms, but I'll poke eedri/dcaro about it <deepakcs> ewoud, thanks, so I won't repost my patches then <ewoud> deepakcs: that looks odd because first it shows an error and then OK <apuimedo> ewoud, deepakcs it is because of el having Python 2.6 instead of 2.7 <ewoud> apuimedo: yes, but then I'd expect it to just show an error and not OK <deepakcs> ewoud, apuimedo thanks. I didn't notice the OK embedded after the error :) <apuimedo> ewoud, yeah... I guess the jenkins job could be better done :P <apuimedo> deepakcs, hopefully today it'll be fixed <apuimedo> by a patch from saggi <ewoud> deepakcs: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/ only shows errors so you're not alone <deepakcs> ewoud, some consolation for me :) <ewoud> deepakcs: I poked dcaro on #vdsm (OFTC) <deepakcs> you mean #ovirt ? <ewoud> euh yes <ewoud> but it can't hurt to send an email to infra@ovirt.org and/or create a ticket in trac <deepakcs> i hope the 'X' against my verified goes away ;) <deepakcs> ewoud, I can do that and paste this chatlog of ours <deepakcs> i mean send mail to the infra team <ewoud> I don't think there's a way to rerun the unit tests unless you push a new set, but there's no point until the job is fixed <deepakcs> ewoud, i thot if they fixed the issue, they will have the test re-run on all the failed patches ? <ewoud> deepakcs: not sure because gerrit triggers a build and not sure if you can easily trigger it again <deepakcs> ok
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro Red Hat Czech s.r.o. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic RHT Global #: 82-62605
Hi Deepak, all patch on vdsm for master branch will fail until this patch is merged: http://gerrit.ovirt.org/#/c/11350/1. danken, either merge the fix, or i will disable the gerrit job for it. otherwise patches will keep getting -1 from jenkins. Eyal. ----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "infra" <infra@ovirt.org> Sent: Thursday, January 24, 2013 4:40:47 PM Subject: Jenkins build failure due to "publish of test report" failing
Hi Infra team, I am getting jenkins build failures for my patches, but it does not seem related to the change I made Pls see the chat I had with ewoud below.
Let me know whether I need to re-post my patches ?
thanx, deepak
<deepakcs> is anybody seeing jenkins unit test failures ? I am getting some @ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/31/console <deepakcs> but they don't seem to be related to my patch changes at all <deepakcs> and the unit tests ran fine on my devpt system ! <deepakcs> fsimonce, ^^ can u provide some insight ? * acathrow (~acathrow@pool-173-76-239-245.bstnma.fios.verizon.net) has left #vdsm <ewoud> deepakcs: maybe the EL job is configgured different from th fedora one? <deepakcs> ewoud, you mean if it had run on fedora, it would have possible passed the test ? <ewoud> deepakcs: if you look at the console output you can see EL tries to publish unit test results where fedora doesn't <ewoud> Build step 'Publish JUnit test result report' changed build result to FAILURE <deepakcs> ewoud, i see some ERROR in untitests too .. related to eth0 / net tests.. which i don't see on my fedora devpt box <deepakcs> ewoud, so whats the next step for me ? resubit and hope that it runs on fedora ? <ewoud> deepakcs: no, it's configured to always run on both <ewoud> current step would be to find a jenkins job admin who can change it <deepakcs> ewoud, not clear to me. the publishing of test is failing, hence the overall build is failing, so someone needs to fix that ? <ewoud> deepakcs: yes, it's misconfigured on EL <ewoud> deepakcs: http://www.ovirt.org/Infrastructure_team_assignments tells me eedri and dcaro are general jenkins admins, but maybe someone in the VDSM team can also configure it <deepakcs> ewoud, wondering why i don't see build failure mails for other patches on the list ? <ewoud> deepakcs: that I don't know <deepakcs> ewoud, any idea abt some of the ERROR seen by the unit tests in that console o/p ? <ewoud> deepakcs: I also think that there should be one job to build vdsm and have it in a grid config so it builds on multiple platforms, but I'll poke eedri/dcaro about it <deepakcs> ewoud, thanks, so I won't repost my patches then <ewoud> deepakcs: that looks odd because first it shows an error and then OK <apuimedo> ewoud, deepakcs it is because of el having Python 2.6 instead of 2.7 <ewoud> apuimedo: yes, but then I'd expect it to just show an error and not OK <deepakcs> ewoud, apuimedo thanks. I didn't notice the OK embedded after the error :) <apuimedo> ewoud, yeah... I guess the jenkins job could be better done :P <apuimedo> deepakcs, hopefully today it'll be fixed <apuimedo> by a patch from saggi <ewoud> deepakcs: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/ only shows errors so you're not alone <deepakcs> ewoud, some consolation for me :) <ewoud> deepakcs: I poked dcaro on #vdsm (OFTC) <deepakcs> you mean #ovirt ? <ewoud> euh yes <ewoud> but it can't hurt to send an email to infra@ovirt.org and/or create a ticket in trac <deepakcs> i hope the 'X' against my verified goes away ;) <deepakcs> ewoud, I can do that and paste this chatlog of ours <deepakcs> i mean send mail to the infra team <ewoud> I don't think there's a way to rerun the unit tests unless you push a new set, but there's no point until the job is fixed <deepakcs> ewoud, i thot if they fixed the issue, they will have the test re-run on all the failed patches ? <ewoud> deepakcs: not sure because gerrit triggers a build and not sure if you can easily trigger it again <deepakcs> ok
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
No, it will keep reporting failures. This is because the EL hosts are misconfigured. Under RHEL 6 the python-nose package does not have the xunit plugin. You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Saggi Mizrahi" <smizrahi@redhat.com> Sent: Thursday, January 24, 2013 11:18:37 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
Hi Deepak,
all patch on vdsm for master branch will fail until this patch is merged: http://gerrit.ovirt.org/#/c/11350/1.
danken, either merge the fix, or i will disable the gerrit job for it. otherwise patches will keep getting -1 from jenkins.
Eyal.
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "infra" <infra@ovirt.org> Sent: Thursday, January 24, 2013 4:40:47 PM Subject: Jenkins build failure due to "publish of test report" failing
Hi Infra team, I am getting jenkins build failures for my patches, but it does not seem related to the change I made Pls see the chat I had with ewoud below.
Let me know whether I need to re-post my patches ?
thanx, deepak
<deepakcs> is anybody seeing jenkins unit test failures ? I am getting some @ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/31/console <deepakcs> but they don't seem to be related to my patch changes at all <deepakcs> and the unit tests ran fine on my devpt system ! <deepakcs> fsimonce, ^^ can u provide some insight ? * acathrow (~acathrow@pool-173-76-239-245.bstnma.fios.verizon.net) has left #vdsm <ewoud> deepakcs: maybe the EL job is configgured different from th fedora one? <deepakcs> ewoud, you mean if it had run on fedora, it would have possible passed the test ? <ewoud> deepakcs: if you look at the console output you can see EL tries to publish unit test results where fedora doesn't <ewoud> Build step 'Publish JUnit test result report' changed build result to FAILURE <deepakcs> ewoud, i see some ERROR in untitests too .. related to eth0 / net tests.. which i don't see on my fedora devpt box <deepakcs> ewoud, so whats the next step for me ? resubit and hope that it runs on fedora ? <ewoud> deepakcs: no, it's configured to always run on both <ewoud> current step would be to find a jenkins job admin who can change it <deepakcs> ewoud, not clear to me. the publishing of test is failing, hence the overall build is failing, so someone needs to fix that ? <ewoud> deepakcs: yes, it's misconfigured on EL <ewoud> deepakcs: http://www.ovirt.org/Infrastructure_team_assignments tells me eedri and dcaro are general jenkins admins, but maybe someone in the VDSM team can also configure it <deepakcs> ewoud, wondering why i don't see build failure mails for other patches on the list ? <ewoud> deepakcs: that I don't know <deepakcs> ewoud, any idea abt some of the ERROR seen by the unit tests in that console o/p ? <ewoud> deepakcs: I also think that there should be one job to build vdsm and have it in a grid config so it builds on multiple platforms, but I'll poke eedri/dcaro about it <deepakcs> ewoud, thanks, so I won't repost my patches then <ewoud> deepakcs: that looks odd because first it shows an error and then OK <apuimedo> ewoud, deepakcs it is because of el having Python 2.6 instead of 2.7 <ewoud> apuimedo: yes, but then I'd expect it to just show an error and not OK <deepakcs> ewoud, apuimedo thanks. I didn't notice the OK embedded after the error :) <apuimedo> ewoud, yeah... I guess the jenkins job could be better done :P <apuimedo> deepakcs, hopefully today it'll be fixed <apuimedo> by a patch from saggi <ewoud> deepakcs: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/ only shows errors so you're not alone <deepakcs> ewoud, some consolation for me :) <ewoud> deepakcs: I poked dcaro on #vdsm (OFTC) <deepakcs> you mean #ovirt ? <ewoud> euh yes <ewoud> but it can't hurt to send an email to infra@ovirt.org and/or create a ticket in trac <deepakcs> i hope the 'X' against my verified goes away ;) <deepakcs> ewoud, I can do that and paste this chatlog of ours <deepakcs> i mean send mail to the infra team <ewoud> I don't think there's a way to rerun the unit tests unless you push a new set, but there's no point until the job is fixed <deepakcs> ewoud, i thot if they fixed the issue, they will have the test re-run on all the failed patches ? <ewoud> deepakcs: not sure because gerrit triggers a build and not sure if you can easily trigger it again <deepakcs> ok
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead.
ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Saggi Mizrahi" <smizrahi@redhat.com> Sent: Thursday, January 24, 2013 11:18:37 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
Hi Deepak,
all patch on vdsm for master branch will fail until this patch is merged: http://gerrit.ovirt.org/#/c/11350/1.
danken, either merge the fix, or i will disable the gerrit job for it. otherwise patches will keep getting -1 from jenkins.
Eyal.
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "infra" <infra@ovirt.org> Sent: Thursday, January 24, 2013 4:40:47 PM Subject: Jenkins build failure due to "publish of test report" failing
Hi Infra team, I am getting jenkins build failures for my patches, but it does not seem related to the change I made Pls see the chat I had with ewoud below.
Let me know whether I need to re-post my patches ?
thanx, deepak
<deepakcs> is anybody seeing jenkins unit test failures ? I am getting some @ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/31/console <deepakcs> but they don't seem to be related to my patch changes at all <deepakcs> and the unit tests ran fine on my devpt system ! <deepakcs> fsimonce, ^^ can u provide some insight ? * acathrow (~acathrow@pool-173-76-239-245.bstnma.fios.verizon.net) has left #vdsm <ewoud> deepakcs: maybe the EL job is configgured different from th fedora one? <deepakcs> ewoud, you mean if it had run on fedora, it would have possible passed the test ? <ewoud> deepakcs: if you look at the console output you can see EL tries to publish unit test results where fedora doesn't <ewoud> Build step 'Publish JUnit test result report' changed build result to FAILURE <deepakcs> ewoud, i see some ERROR in untitests too .. related to eth0 / net tests.. which i don't see on my fedora devpt box <deepakcs> ewoud, so whats the next step for me ? resubit and hope that it runs on fedora ? <ewoud> deepakcs: no, it's configured to always run on both <ewoud> current step would be to find a jenkins job admin who can change it <deepakcs> ewoud, not clear to me. the publishing of test is failing, hence the overall build is failing, so someone needs to fix that ? <ewoud> deepakcs: yes, it's misconfigured on EL <ewoud> deepakcs: http://www.ovirt.org/Infrastructure_team_assignments tells me eedri and dcaro are general jenkins admins, but maybe someone in the VDSM team can also configure it <deepakcs> ewoud, wondering why i don't see build failure mails for other patches on the list ? <ewoud> deepakcs: that I don't know <deepakcs> ewoud, any idea abt some of the ERROR seen by the unit tests in that console o/p ? <ewoud> deepakcs: I also think that there should be one job to build vdsm and have it in a grid config so it builds on multiple platforms, but I'll poke eedri/dcaro about it <deepakcs> ewoud, thanks, so I won't repost my patches then <ewoud> deepakcs: that looks odd because first it shows an error and then OK <apuimedo> ewoud, deepakcs it is because of el having Python 2.6 instead of 2.7 <ewoud> apuimedo: yes, but then I'd expect it to just show an error and not OK <deepakcs> ewoud, apuimedo thanks. I didn't notice the OK embedded after the error :) <apuimedo> ewoud, yeah... I guess the jenkins job could be better done :P <apuimedo> deepakcs, hopefully today it'll be fixed <apuimedo> by a patch from saggi <ewoud> deepakcs: http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/ only shows errors so you're not alone <deepakcs> ewoud, some consolation for me :) <ewoud> deepakcs: I poked dcaro on #vdsm (OFTC) <deepakcs> you mean #ovirt ? <ewoud> euh yes <ewoud> but it can't hurt to send an email to infra@ovirt.org and/or create a ticket in trac <deepakcs> i hope the 'X' against my verified goes away ;) <deepakcs> ewoud, I can do that and paste this chatlog of ours <deepakcs> i mean send mail to the infra team <ewoud> I don't think there's a way to rerun the unit tests unless you push a new set, but there's no point until the job is fixed <deepakcs> ewoud, i thot if they fixed the issue, they will have the test re-run on all the failed patches ? <ewoud> deepakcs: not sure because gerrit triggers a build and not sure if you can easily trigger it again <deepakcs> ok
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below... http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/ Wondering if the job was re-run for the above patches after the issue was fixed ? thanx, deepak
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com> Sent: Friday, January 25, 2013 6:10:57 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below...
http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue was fixed ?
if it still has x, it means it wasn't fix. please talk to saggi/danken for providing a fix for it.
thanx, deepak
On Fri, Jan 25, 2013 at 01:36:42AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com> Sent: Friday, January 25, 2013 6:10:57 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below...
http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue was fixed ?
if it still has x, it means it wasn't fix. please talk to saggi/danken for providing a fix for it.
Currently tests are failing because of nose not being installed on the slave. Only when nose exists it's time to blame danken. """ from nose import config ImportError: No module named nose """ http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/75/console
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org> Sent: Saturday, January 26, 2013 3:55:05 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
On Fri, Jan 25, 2013 at 01:36:42AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com> Sent: Friday, January 25, 2013 6:10:57 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below...
http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue was fixed ?
if it still has x, it means it wasn't fix. please talk to saggi/danken for providing a fix for it.
Currently tests are failing because of nose not being installed on the slave. Only when nose exists it's time to blame danken.
i did exactly as saggi requested. removed python-nose and installed python-nose1.1 (with symlink).
""" from nose import config ImportError: No module named nose """
http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/75/console
On Sat, Jan 26, 2013 at 11:53:36AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org> Sent: Saturday, January 26, 2013 3:55:05 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
On Fri, Jan 25, 2013 at 01:36:42AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com> Sent: Friday, January 25, 2013 6:10:57 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message -----
From: "Saggi Mizrahi" <smizrahi@redhat.com> To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> Sent: Thursday, January 24, 2013 6:35:36 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
No, it will keep reporting failures. This is because the EL hosts are misconfigured.
Under RHEL 6 the python-nose package does not have the xunit plugin.
You need to remove it install the python-nose1.1 package and make an alias or alternatively make the makefile detect that nosetests is missing and call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below...
http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue was fixed ?
if it still has x, it means it wasn't fix. please talk to saggi/danken for providing a fix for it.
Currently tests are failing because of nose not being installed on the slave. Only when nose exists it's time to blame danken.
i did exactly as saggi requested. removed python-nose and installed python-nose1.1 (with symlink).
Would you add anothor softlink ln -s /usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose /usr/lib/python2.6/site-packages/nose and verify that `pydoc nose` and the following works.
""" from nose import config ImportError: No module named nose """
http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/75/console
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org> Sent: Sunday, January 27, 2013 1:21:38 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
On Sat, Jan 26, 2013 at 11:53:36AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com>, "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org> Sent: Saturday, January 26, 2013 3:55:05 PM Subject: Re: Jenkins build failure due to "publish of test report" failing
On Fri, Jan 25, 2013 at 01:36:42AM -0500, Eyal Edri wrote:
----- Original Message -----
From: "Deepak C Shetty" <deepakcs@linux.vnet.ibm.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Saggi Mizrahi" <smizrahi@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com> Sent: Friday, January 25, 2013 6:10:57 AM Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
----- Original Message ----- > From: "Saggi Mizrahi" <smizrahi@redhat.com> > To: "Eyal Edri" <eedri@redhat.com>, "Dan Kenigsberg" > <danken@redhat.com> > Cc: "infra" <infra@ovirt.org>, "Deepak C Shetty" > <deepakcs@linux.vnet.ibm.com> > Sent: Thursday, January 24, 2013 6:35:36 PM > Subject: Re: Jenkins build failure due to "publish of test > report" > failing > > No, it will keep reporting failures. > This is because the EL hosts are misconfigured. > > Under RHEL 6 the python-nose package does not have the > xunit > plugin. > > You need to remove it install the python-nose1.1 package > and > make > an > alias or alternatively make the makefile detect that > nosetests > is > missing and > call nosetests1.1 instead. ok, i installed nose1.1 on both el hosts, and added link to /usr/bin/nosetests.
Hi Eyal, I still see the 'X' mark by jenkins for some of my patches as below...
http://gerrit.ovirt.org/#/c/10196/ http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue was fixed ?
if it still has x, it means it wasn't fix. please talk to saggi/danken for providing a fix for it.
Currently tests are failing because of nose not being installed on the slave. Only when nose exists it's time to blame danken.
i did exactly as saggi requested. removed python-nose and installed python-nose1.1 (with symlink).
Would you add anothor softlink
ln -s /usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose /usr/lib/python2.6/site-packages/nose
and verify that `pydoc nose` and the following works.
added, any verified with pydoc nose. re-rerunning jobs now.
""" from nose import config ImportError: No module named nose """
http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/75/console
participants (5)
-
Dan Kenigsberg -
David Caro -
Deepak C Shetty -
Eyal Edri -
Saggi Mizrahi