Graham,
I've turned it essentially into a no-op now. i'll let the original
authors debate the full revert and other implications.
Thanks,
Dims
On Sun, Jan 29, 2017 at 3:42 PM, Hayes, Graham wrote:
> On 29/01/2017 15:45, Davanum Srinivas wrote:
>> Graham, Sławek, Joshua,
>>
>> Please take a look
Hello,
My patch [1] to fix it in Neutron is now merged. Thx Ihar and Kevin for
so fast review :)
It looks that now functional tests are working fine.
[1] https://review.openstack.org/#/c/426550/
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On Sun, 29 Jan 2017, Sławek Kapło
On 29/01/2017 15:45, Davanum Srinivas wrote:
> Graham, Sławek, Joshua,
>
> Please take a look at my attempt:
> https://review.openstack.org/#/c/426576/
>
> Thanks,
> Dims
>
At this point, a full revert seems like the right idea.
There is a few problem with the warning, not just the amount of them
Graham, Sławek, Joshua,
Please take a look at my attempt:
https://review.openstack.org/#/c/426576/
Thanks,
Dims
On Sun, Jan 29, 2017 at 7:56 AM, Hayes, Graham wrote:
> On 29/01/17 00:53, Davanum Srinivas wrote:
>> Graham, Sławek,
>>
>> Have you seen this?
>>
>> Neutron has/uses a WarningFixture
On 29/01/17 00:53, Davanum Srinivas wrote:
> Graham, Sławek,
>
> Have you seen this?
>
> Neutron has/uses a WarningFixture:
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
>
> Whic
Hello,
I made small patch to Neutron to fix [1] this issue. It looks that
functional tests are fine with it [2].
Please review it if it makes sense for You :)
[1] https://review.openstack.org/#/c/426550/
[2]
http://logs.openstack.org/50/426550/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/4
Hello,
Thanks for explaining that. I'm don't know this part well and that's why
I asked here if it's oslo or neutron issue.
So it looks like it is issue in Neutron nor Oslo.context, right?
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On Sat, 28 Jan 2017, Joshua Harlow wrote
Yup, all that should be needed is to read the docs and adjust it.
"once" - print only the first occurrence of matching warnings,
regardless of location
"always" - always print matching warnings
Changing it to 'once' should gather less repeated logs; IMHO 'always'
should never be used, so tha
Graham, Sławek,
Have you seen this?
Neutron has/uses a WarningFixture:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
Which uses filterwarnings:
http://git.openstack.org/cgit/openstac
Hello,
Thanks. I just filled bug report to oslo project:
https://bugs.launchpad.net/oslo.context/+bug/1660088
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On Sat, 28 Jan 2017, Hayes, Graham wrote:
> On 28/01/17 20:54, Sławek Kapłoński wrote:
> > Hello,
> >
> > I pushed to
On 28/01/17 20:54, Sławek Kapłoński wrote:
> Hello,
>
> I pushed today patch in Neutron to gerrit [1] and I noticed that functional
> tests are failing. In logs there is huge number of deprecation warnings
> displayed [2]. Tests are failing because of global timeout is reached and IMO
> reason
Hello,
I pushed today patch in Neutron to gerrit [1] and I noticed that functional
tests are failing. In logs there is huge number of deprecation warnings
displayed [2]. Tests are failing because of global timeout is reached and IMO
reason of this timeout is this huge amount of deprecation warn
12 matches
Mail list logo