Re: [openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes

2018-08-06 Thread Ghanshyam Mann
On Sun, 05 Aug 2018 06:44:26 +0900 Matt Riedemann wrote > I've reported a nova bug for this: > > https://bugs.launchpad.net/nova/+bug/1785425 > > But I'm not sure what is the best way to fix it now with the zuul v3 > hotness. We had an irrelevant-files entry in

Re: [openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes

2018-08-04 Thread Doug Hellmann
Excerpts from Matt Riedemann's message of 2018-08-04 16:44:26 -0500: > I've reported a nova bug for this: > > https://bugs.launchpad.net/nova/+bug/1785425 > > But I'm not sure what is the best way to fix it now with the zuul v3 > hotness. We had an irrelevant-files entry in project-config for

[openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes

2018-08-04 Thread Matt Riedemann
I've reported a nova bug for this: https://bugs.launchpad.net/nova/+bug/1785425 But I'm not sure what is the best way to fix it now with the zuul v3 hotness. We had an irrelevant-files entry in project-config for the tempest-full job but we don't have that for tempest-full-py3, so should we