On 05/27/2016 02:30 PM, Raildo Mascena wrote:
In addition, I'm the one of the folks who are working with the v3-only
gates, the main case that we are looking for is when the functional
job is working and the the v3-only is not, so everything related to
this jobs, you can just ping me on irc.
In addition, I'm the one of the folks who are working with the v3-only
gates, the main case that we are looking for is when the functional job is
working and the the v3-only is not, so everything related to this jobs, you
can just ping me on irc. :)
Cheers,
Raildo
On Thu, May 26, 2016 at 6:27
The function-nv was depending of a first test to be merged =)
The v3 depends directly on it, the difference is that it passes a flag to
deactivate v2.0 in devstack.
On Thu, May 26, 2016 at 5:48 PM, Steve Martinelli
wrote:
> On Thu, May 26, 2016 at 12:59 PM, Adam Young
On Thu, May 26, 2016 at 12:59 PM, Adam Young wrote:
> On 05/26/2016 11:36 AM, Morgan Fainberg wrote:
>
>
>
> On Thu, May 26, 2016 at 7:55 AM, Adam Young wrote:
>
>> Some mix of these three tests is almost always failing:
>>
>>
On 05/26/2016 11:36 AM, Morgan Fainberg wrote:
On Thu, May 26, 2016 at 7:55 AM, Adam Young > wrote:
Some mix of these three tests is almost always failing:
gate-keystone-dsvm-functional-nv FAILURE in 20m 04s (non-voting)
On Thu, May 26, 2016 at 7:55 AM, Adam Young wrote:
> Some mix of these three tests is almost always failing:
>
> gate-keystone-dsvm-functional-nv FAILURE in 20m 04s (non-voting)
> gate-keystone-dsvm-functional-v3-only-nv FAILURE in 32m 45s (non-voting)
>
Some mix of these three tests is almost always failing:
gate-keystone-dsvm-functional-nv FAILURE in 20m 04s (non-voting)
gate-keystone-dsvm-functional-v3-only-nv FAILURE in 32m 45s (non-voting)
gate-tempest-dsvm-keystone-uwsgi-full-nv FAILURE in 1h 07m 53s (non-voting)
Are we going to keep