----- Original Message -----
From: "Antoni Segura Puimedon" asegurap@redhat.com To: "Francesco Romani" fromani@redhat.com Cc: "Dan Kenigsberg" danken@redhat.com, devel@ovirt.org, vered@redhat.com, dougsland@redhat.com Sent: Thursday, April 3, 2014 5:28:05 PM Subject: Re: Vdsm functional tests
I know virt functional tests arent' comprehensive and can be improved, but I'm not aware of any major drawback about them (e.g. unbearable slowness, resource leak...). Am I missing something big here?
Well, in order to activate them we should have them consistently passing on master/ovirt-3.4 to know that they are not broken. If that is the case. Let's work in making the jenkins job.
That's right. I recently runned them an handful of time on RHEL6.5 and Fedora19 and they seems OK.
If we can try activate them on jenkins, I volunteer to babysit them at least initially to ensure everything is right (note: I don't have SSH access to the jenkins boxes).
If more extensive analysis/investigation/check is needed, I volunteer for that as well, but I'm afraid this will require a couple of days.
Bests,
----- Original Message -----
From: "Francesco Romani" fromani@redhat.com To: "Antoni Segura Puimedon" asegurap@redhat.com Cc: "Dan Kenigsberg" danken@redhat.com, devel@ovirt.org, vered@redhat.com, dougsland@redhat.com, "vdsm-devel" vdsm-devel@lists.fedorahosted.org Sent: Thursday, April 3, 2014 5:34:52 PM Subject: Re: Vdsm functional tests
----- Original Message -----
From: "Antoni Segura Puimedon" asegurap@redhat.com To: "Francesco Romani" fromani@redhat.com Cc: "Dan Kenigsberg" danken@redhat.com, devel@ovirt.org, vered@redhat.com, dougsland@redhat.com Sent: Thursday, April 3, 2014 5:28:05 PM Subject: Re: Vdsm functional tests
I know virt functional tests arent' comprehensive and can be improved, but I'm not aware of any major drawback about them (e.g. unbearable slowness, resource leak...). Am I missing something big here?
Well, in order to activate them we should have them consistently passing on master/ovirt-3.4 to know that they are not broken. If that is the case. Let's work in making the jenkins job.
That's right. I recently runned them an handful of time on RHEL6.5 and Fedora19 and they seems OK.
If we can try activate them on jenkins, I volunteer to babysit them at least initially to ensure everything is right (note: I don't have SSH access to the jenkins boxes).
If more extensive analysis/investigation/check is needed, I volunteer for that as well, but I'm afraid this will require a couple of days.
Let's do it tomorrow then.
Bests,
-- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
On Apr 3, 2014, at 17:37 , Antoni Segura Puimedon asegurap@redhat.com wrote:
----- Original Message -----
From: "Francesco Romani" fromani@redhat.com To: "Antoni Segura Puimedon" asegurap@redhat.com Cc: "Dan Kenigsberg" danken@redhat.com, devel@ovirt.org, vered@redhat.com, dougsland@redhat.com, "vdsm-devel" vdsm-devel@lists.fedorahosted.org Sent: Thursday, April 3, 2014 5:34:52 PM Subject: Re: Vdsm functional tests
----- Original Message -----
From: "Antoni Segura Puimedon" asegurap@redhat.com To: "Francesco Romani" fromani@redhat.com Cc: "Dan Kenigsberg" danken@redhat.com, devel@ovirt.org, vered@redhat.com, dougsland@redhat.com Sent: Thursday, April 3, 2014 5:28:05 PM Subject: Re: Vdsm functional tests
I know virt functional tests arent' comprehensive and can be improved, but I'm not aware of any major drawback about them (e.g. unbearable slowness, resource leak...). Am I missing something big here?
Well, in order to activate them we should have them consistently passing on master/ovirt-3.4 to know that they are not broken. If that is the case. Let's work in making the jenkins job.
That's right. I recently runned them an handful of time on RHEL6.5 and Fedora19 and they seems OK.
If we can try activate them on jenkins, I volunteer to babysit them at least initially to ensure everything is right (note: I don't have SSH access to the jenkins boxes).
If more extensive analysis/investigation/check is needed, I volunteer for that as well, but I'm afraid this will require a couple of days.
Let's do it tomorrow then.
Martin took a look yesterday as well. It seems other than initial startup problem, may be related to slow vdsm start….there is a lame "sleep 10"...should be solved by better init part of the test script And then let's roll!
as a reminder - no arbitrary sleeps please! Anywhere.
Thanks, michal
Bests,
-- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
vdsm-devel@lists.fedorahosted.org