Another test failure which is not related to the tested patch
Hi infra, Please look at this unrelated test failure: http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/1151/... 18:57:00 INFO: installing package(s): autoconf make autoreconf gettext-devel make automake pyflakes python-pep8 libvirt-python python-devel python-nose sanlock-python python-ordereddict python-pthreading libselinux-python python-ethtool m2crypto python-dmidecode python-netaddr python-inotify python-argparse git python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl libtool gettext-devel python-ioprocess python-six 18:58:51 ERROR: Command failed. See logs for output. Patch: https://gerrit.ovirt.org/41862 This failure is not related to vdsm and in particular to this patch. Nir
--tVmo9FyGdCe4F4YN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It seems fedora repos for epel are not working well, that's outside our han= ds. We can try to pass it through our current experimental squid, it requires s= ome reconfiguration though (@eyal, please open a task on it if you think it's relevant). Best we can do now is retry. Do you have any better suggestion on how to handle this type of issues? I'm open to any suggestion. On 06/05, Nir Soffer wrote:
Hi infra, =20 Please look at this unrelated test failure: =20 http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/11= 51/console =20 18:57:00 INFO: installing package(s): autoconf make autoreconf gettext-de= vel make automake pyflakes python-pep8 libvirt-python python-devel python-n= ose sanlock-python python-ordereddict python-pthreading libselinux-python p= ython-ethtool m2crypto python-dmidecode python-netaddr python-inotify pytho= n-argparse git python-cpopen bridge-utils libguestfs-tools-c pyparted opens= sl libnl libtool gettext-devel python-ioprocess python-six 18:58:51 ERROR: Command failed. See logs for output. =20 Patch: https://gerrit.ovirt.org/41862 =20 This failure is not related to vdsm and in particular to this patch. =20 Nir =20 =20 =20 =20 =20
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --tVmo9FyGdCe4F4YN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVcijmAAoJEEBxx+HSYmnDE7MH/3HsmJYIihj8Qrpzh5t4nQyv /M8o0Rv7GUUN71Zjd++lWxbNibuu7z9kSrjtn/StEky+MfTQrlrukOKIICr0eDjv mjgpiZE4PJEk++/9DlxE7gvOfgQ+1hqGPaQdzV7TzTCvYwoHvcCLE5Q0xyNyCia5 54wzty4o8HjP/P3AVVPM7WUA8Chu87FKsDlC0zmcc4f1s0Ebm9fPMg8i2ZSmCD+W b6/KVSokiVTWgEf1YL+Oe+wEPyC5qgWq64d4nCzJWlVHD+z3GVEcwCAaELzFhiXS Wnh1CIrX8EXrUSdKEECByt2Gti6D/87iJNzZWzrrKAiueGVfz5T8KdOuUMfhpY4= =iqkx -----END PGP SIGNATURE----- --tVmo9FyGdCe4F4YN--
Hi, thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them. i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel? another option is to change timeout mirror setting for epel to be more forgiven. both require a ticket [2] as david said, if we want to add it to the infra team work plan. but, we will never have 100% error free environment, as we are dependent on various aspects of the infra, like network stability. if you have other suggestions / solutions on how to solve these, we're always open to hear. so as david said, quickest solution will be to rerun the job using the manual runner [3] if it was a gerrit instance, or just retry it if its a normal merged job. [1] http://download.fedoraproject.org/pub/epel/testing/7/x86_64/i/ioprocess-0.15...: [Errno 12] Timeout on http://mirrors.einstein.yu.edu/epel/testing/7/x86_64/i/ioprocess-0.15.0-2.el...: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds') [2] https://ovirt-jira.atlassian.net/secure/Dashboard.jspa [3] http://jenkins.ovirt.org/gerrit_manual_trigger/ ----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Eyal Edri" <eedri@redhat.com>, "infra" <infra@ovirt.org> Sent: Saturday, June 6, 2015 1:55:34 AM Subject: Re: Another test failure which is not related to the tested patch
It seems fedora repos for epel are not working well, that's outside our hands. We can try to pass it through our current experimental squid, it requires some reconfiguration though (@eyal, please open a task on it if you think it's relevant).
Best we can do now is retry.
Do you have any better suggestion on how to handle this type of issues? I'm open to any suggestion.
On 06/05, Nir Soffer wrote:
Hi infra,
Please look at this unrelated test failure:
http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/1151/...
18:57:00 INFO: installing package(s): autoconf make autoreconf gettext-devel make automake pyflakes python-pep8 libvirt-python python-devel python-nose sanlock-python python-ordereddict python-pthreading libselinux-python python-ethtool m2crypto python-dmidecode python-netaddr python-inotify python-argparse git python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl libtool gettext-devel python-ioprocess python-six 18:58:51 ERROR: Command failed. See logs for output.
Patch: https://gerrit.ovirt.org/41862
This failure is not related to vdsm and in particular to this patch.
Nir
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Il 06/06/2015 11:57, Eyal Edri ha scritto:
Hi,
thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them.
i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel?
We can't disable epel testing since ioprocess is not yet in stable repo.
another option is to change timeout mirror setting for epel to be more forgiven.
Or create a local mirror with just the needed packages.
both require a ticket [2] as david said, if we want to add it to the infra team work plan. but, we will never have 100% error free environment, as we are dependent on various aspects of the infra, like network stability. if you have other suggestions / solutions on how to solve these, we're always open to hear.
so as david said, quickest solution will be to rerun the job using the manual runner [3] if it was a gerrit instance, or just retry it if its a normal merged job.
[1] http://download.fedoraproject.org/pub/epel/testing/7/x86_64/i/ioprocess-0.15...: [Errno 12] Timeout on http://mirrors.einstein.yu.edu/epel/testing/7/x86_64/i/ioprocess-0.15.0-2.el...: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
[2] https://ovirt-jira.atlassian.net/secure/Dashboard.jspa
[3] http://jenkins.ovirt.org/gerrit_manual_trigger/
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Eyal Edri" <eedri@redhat.com>, "infra" <infra@ovirt.org> Sent: Saturday, June 6, 2015 1:55:34 AM Subject: Re: Another test failure which is not related to the tested patch
It seems fedora repos for epel are not working well, that's outside our hands. We can try to pass it through our current experimental squid, it requires some reconfiguration though (@eyal, please open a task on it if you think it's relevant).
Best we can do now is retry.
Do you have any better suggestion on how to handle this type of issues? I'm open to any suggestion.
On 06/05, Nir Soffer wrote:
Hi infra,
Please look at this unrelated test failure:
http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/1151/...
18:57:00 INFO: installing package(s): autoconf make autoreconf gettext-devel make automake pyflakes python-pep8 libvirt-python python-devel python-nose sanlock-python python-ordereddict python-pthreading libselinux-python python-ethtool m2crypto python-dmidecode python-netaddr python-inotify python-argparse git python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl libtool gettext-devel python-ioprocess python-six 18:58:51 ERROR: Command failed. See logs for output.
Patch: https://gerrit.ovirt.org/41862
This failure is not related to vdsm and in particular to this patch.
Nir
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote:
Il 06/06/2015 11:57, Eyal Edri ha scritto:
Hi,
thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them.
i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel?
We can't disable epel testing since ioprocess is not yet in stable repo.
(btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess )
On 06/08/2015 03:39 PM, Dan Kenigsberg wrote:
On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote:
Il 06/06/2015 11:57, Eyal Edri ha scritto:
Hi,
thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them.
i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel?
We can't disable epel testing since ioprocess is not yet in stable repo.
(btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess )
Its just clicking in the package page title "push to stable" so I did it probably it will be there in few days -- Yaniv Bronhaim.
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Dan Kenigsberg" <danken@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, ykaplan@redhat.com Cc: "Eyal Edri" <eedri@redhat.com>, "infra" <infra@ovirt.org> Sent: Monday, June 8, 2015 6:59:40 PM Subject: Re: Another test failure which is not related to the tested patch
On 06/08/2015 03:39 PM, Dan Kenigsberg wrote:
On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote:
Il 06/06/2015 11:57, Eyal Edri ha scritto:
Hi,
thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them.
i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel?
We can't disable epel testing since ioprocess is not yet in stable repo.
(btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess )
Its just clicking in the package page title "push to stable" so I did it probably it will be there in few days
sandro, after these are published, can we drop the testing repos from the mock jobs?
-- Yaniv Bronhaim. _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
Il 09/06/2015 10:02, Eyal Edri ha scritto:
----- Original Message -----
From: "ybronhei" <ybronhei@redhat.com> To: "Dan Kenigsberg" <danken@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, ykaplan@redhat.com Cc: "Eyal Edri" <eedri@redhat.com>, "infra" <infra@ovirt.org> Sent: Monday, June 8, 2015 6:59:40 PM Subject: Re: Another test failure which is not related to the tested patch
On 06/08/2015 03:39 PM, Dan Kenigsberg wrote:
On Mon, Jun 08, 2015 at 08:06:28AM +0200, Sandro Bonazzola wrote:
Il 06/06/2015 11:57, Eyal Edri ha scritto:
Hi,
thanks for reporting this nir, this is helping us map the current infra issues at hand and try to resolve them.
i see the failing repos [1] are from epel/testing - are these mandatory to the test? or we can disable them and use only stable epel?
We can't disable epel testing since ioprocess is not yet in stable repo.
(btw Yeela/Yaniv, can you push the latest build to stable? https://admin.fedoraproject.org/updates/search/ioprocess )
Its just clicking in the package page title "push to stable" so I did it probably it will be there in few days
sandro, after these are published, can we drop the testing repos from the mock jobs?
We can try and see if something is missing. I've not all the requirments for all the packages at hand.
-- Yaniv Bronhaim. _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (6)
-
Dan Kenigsberg -
David Caro -
Eyal Edri -
Nir Soffer -
Sandro Bonazzola -
ybronhei