On 3/29/2018 2:44 AM, Radoslav Gerganov wrote:
While running the VMware CI continues to be a challenge, I must say this
patch fixes a regression introduced by Matt Riedemann's patch:
https://review.openstack.org/#/c/549411/
for which the VMware CI clearly indicated there was a problem and
On 3/29/2018 7:53 AM, William M Edmonds wrote:
running only on virt/vmwareapi changes would not catch problems caused
by changes elsewhere, such as compute/manager.py or virt/driver.py
Right, I think virt driver 3rd party CI should run on at least some
select sub-trees, the major ones that
On 3/29/2018 5:19 AM, melanie witt wrote:
Thanks. Just curious, how is the CI passing if the driver is currently
broken for detach_volume? I had thought maybe particular tests were
skipped in response to my original email that linked the bug fix patch,
but it looks like that run was from
melanie witt wrote on 03/29/2018 06:03:26 AM:
> I would like to see the VMware CI running again and it need only run on
> changes under the nova/virt/vmwareapi/ tree, to save on your resources.
> And on our side, I'd like us to add VMware subteam members to VMware
> driver
On Thu, 29 Mar 2018 10:09:09 +, Gary Kotton wrote:
Here is an example where the CI has run on a recent patch - yesterday
-https://review.openstack.org/557256
Thanks. Just curious, how is the CI passing if the driver is currently
broken for detach_volume? I had thought maybe particular
Hi,
Here is an example where the CI has run on a recent patch - yesterday -
https://review.openstack.org/557256
Thanks
Gary
On 3/29/18, 1:04 PM, "melanie witt" wrote:
On Thu, 29 Mar 2018 10:44:52 +0300, Radoslav Gerganov wrote:
> On 28.03.2018 19:07, melanie witt
On Thu, 29 Mar 2018 10:44:52 +0300, Radoslav Gerganov wrote:
On 28.03.2018 19:07, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we noticed it
appears that the VMware NSX CI is no longer running, not even on only the
nova/virt/vmwareapi/ tree.
From the
On 28.03.2018 19:07, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we noticed it
appears that the VMware NSX CI is no longer running, not even on only the
nova/virt/vmwareapi/ tree.
From the third-party CI dashboard, I see some claims of it running but
On Wed, 28 Mar 2018, melanie witt wrote:
Can anyone from the vmware subteam comment on whether or not the vmware
third-party CI is going to be fixed or if it has been abandoned?
I've got no substantive information yet, but for the sake of the
thread not looking ignored, I can report that the
On 3/28/2018 11:07 AM, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we
noticed it appears that the VMware NSX CI is no longer running, not even
on only the nova/virt/vmwareapi/ tree.
From the third-party CI dashboard, I see some claims of it running but
Hello everyone,
We were reviewing a bug fix for the vmware driver [0] today and we
noticed it appears that the VMware NSX CI is no longer running, not even
on only the nova/virt/vmwareapi/ tree.
From the third-party CI dashboard, I see some claims of it running but
when I open the patches,
11 matches
Mail list logo