Re: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

2016-06-15 Thread Ian Cordasco
 

-Original Message-
From: gordon chung 
Reply: gordon chung 
Date: June 14, 2016 at 21:14:17
To: Ian Cordasco , OpenStack Development Mailing List 
(not for usage questions) 
Subject:  Re: [openstack-dev] [ceilometer] [stable] Re: 
[Openstack-stable-maint] Stable check of openstack/ceilometer failed

> that's strange, i tried to see if it's just Ceilometer. the
> periodic-neutron-python27-liberty job seems to be capped appropriately
> to oslo.utils 3.2.0. maybe it's a dependency? the
> periodic-nova-python27-liberty job doesn't seem to have any entries
> since March so i can't verify that.

So I looked at 
http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-liberty/3adba17/tox/py27-1.log.txt
 which comes from the latest stable/liberty periodic job failure: 
http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-liberty/3adba17/testr_results.html.gz
 and it if search for oslo.utils it's installing 3.13.0 from requirements.txt.

Perhaps something regressed on stable/liberty?
--  
Ian Cordasco


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

2016-06-14 Thread gordon chung


On 14/06/2016 12:10 PM, Ian Cordasco wrote:
> I wonder why more projects aren't seeing this in stable/liberty. Perhaps, 
> ceilometer stable/liberty isn't using upper-constraints? I think oslo.utils 
> 3.2.0 
> (https://github.com/openstack/requirements/blob/stable/liberty/upper-constraints.txt#L202)
>  is low enough to avoid this if you're using constraints. (It looks as if the 
> total_seconds removal was first released in 3.12.0 
> https://github.com/openstack/oslo.utils/commit/8f5e65cae3aaf8d0a89d16d8932c266151de44f7)
>
that's strange, i tried to see if it's just Ceilometer. the 
periodic-neutron-python27-liberty job seems to be capped appropriately 
to oslo.utils 3.2.0. maybe it's a dependency? the 
periodic-nova-python27-liberty job doesn't seem to have any entries 
since March so i can't verify that.

cheers,

-- 
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

2016-06-14 Thread Ian Cordasco
 

-Original Message-
From: gordon chung 
Reply: OpenStack Development Mailing List (not for usage questions) 

Date: June 14, 2016 at 06:51:08
To: openstack-dev@lists.openstack.org 
Subject:  Re: [openstack-dev] [ceilometer] [stable] Re: 
[Openstack-stable-maint] Stable check of openstack/ceilometer failed

> i don't know if anyone is looking at this -- i'm not sure where this test is 
> even run. i usually  
> let mriedem yell at me but i take it he has bigger things on his plate now :)

Heh, I just looked through these quickly yesterday. I suspect Matt would have 
worked his way around to these.

> this seems like a pretty simple fix from the error output[1]. i guess my 
> question is: should  
> the correct fix be to cap oslo.utils? based on the error, the issue seems to 
> be total_seconds  
> method was removed. this was deprecated in Mitaka[2], so i don't think it 
> should've been  
> removed from Liberty. as this is an easy fix, i'm pretty indifferent if we 
> decide to fix  
> this rather than slow down progress. the original purpose of this method 
> (based on commit  
> messsage) seems to be related to py2.6. i don't know if this is still an 
> issue.

I wonder why more projects aren't seeing this in stable/liberty. Perhaps, 
ceilometer stable/liberty isn't using upper-constraints? I think oslo.utils 
3.2.0 
(https://github.com/openstack/requirements/blob/stable/liberty/upper-constraints.txt#L202)
 is low enough to avoid this if you're using constraints. (It looks as if the 
total_seconds removal was first released in 3.12.0 
https://github.com/openstack/oslo.utils/commit/8f5e65cae3aaf8d0a89d16d8932c266151de44f7)

I'll let soemone else determine if the right answer is capping stable/liberty.

Cheers,
--  
Ian Cordasco


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

2016-06-14 Thread gordon chung
i don't know if anyone is looking at this -- i'm not sure where this test is 
even run. i usually let mriedem yell at me but i take it he has bigger things 
on his plate now :)

this seems like a pretty simple fix from the error output[1]. i guess my 
question is: should the correct fix be to cap oslo.utils? based on the error, 
the issue seems to be total_seconds method was removed. this was deprecated in 
Mitaka[2], so i don't think it should've been removed from Liberty. as this is 
an easy fix, i'm pretty indifferent if we decide to fix this rather than slow 
down progress. the original purpose of this method (based on commit messsage) 
seems to be related to py2.6. i don't know if this is still an issue.

[1] http://paste.openstack.org/show/515960/
[2] https://review.openstack.org/#/c/248590/

cheers,

--
gord


From: Ian Cordasco 
Sent: June 13, 2016 10:01:34 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] 
Stable check of openstack/ceilometer failed

-Original Message-
From: A mailing list for the OpenStack Stable Branch test reports.

Reply: openstack-dev@lists.openstack.org 
Date: June 13, 2016 at 01:13:54
To: openstack-stable-ma...@lists.openstack.org

Subject:  [Openstack-stable-maint] Stable check of openstack/ceilometer failed

> Build failed.
>
> - periodic-ceilometer-docs-liberty 
> http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-liberty/204fcec/
> : SUCCESS in 5m 31s
> - periodic-ceilometer-python27-liberty 
> http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-liberty/00f7474/
> : FAILURE in 6m 20s

Hey ceilometer stable maintainers,

The following tests have been failing in periodic jobs for the last 4 days:

ceilometer.tests.unit.alarm.evaluator.test_base.TestEvaluatorBaseClass

- test_base_time_constraints_by_month
- test_base_time_constraints_complex
- test_base_time_constraints
- test_base_time_constraints_timezone

ceilometer.tests.unit.alarm.evaluator.test_combination.TestEvaluate

- test_no_state_change_outside_time_constraint
- test_state_change_inside_time_constraint

ceilometer.tests.unit.alarm.evaluator.test_gnocchi.TestGnocchiThresholdEvaluate

- test_no_state_change_outside_time_constraint

ceilometer.tests.unit.alarm.evaluator.test_threshold.TestEvaluate

- test_no_state_change_outside_time_constraint
- test_state_change_inside_time_constraint

And this one has been failing every day for almost a week now
(starting on 7 June 2016)

ceilometer.tests.unit.test_messaging.MessagingTests.test_get_transport_optional

Is anyone looking into these?

--
Ian Cordasco

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

2016-06-13 Thread Ian Cordasco
-Original Message-
From: A mailing list for the OpenStack Stable Branch test reports.

Reply: openstack-dev@lists.openstack.org 
Date: June 13, 2016 at 01:13:54
To: openstack-stable-ma...@lists.openstack.org

Subject:  [Openstack-stable-maint] Stable check of openstack/ceilometer failed

> Build failed.
>
> - periodic-ceilometer-docs-liberty 
> http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-liberty/204fcec/
> : SUCCESS in 5m 31s
> - periodic-ceilometer-python27-liberty 
> http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-liberty/00f7474/
> : FAILURE in 6m 20s

Hey ceilometer stable maintainers,

The following tests have been failing in periodic jobs for the last 4 days:

ceilometer.tests.unit.alarm.evaluator.test_base.TestEvaluatorBaseClass

- test_base_time_constraints_by_month
- test_base_time_constraints_complex
- test_base_time_constraints
- test_base_time_constraints_timezone

ceilometer.tests.unit.alarm.evaluator.test_combination.TestEvaluate 

- test_no_state_change_outside_time_constraint
- test_state_change_inside_time_constraint

ceilometer.tests.unit.alarm.evaluator.test_gnocchi.TestGnocchiThresholdEvaluate

- test_no_state_change_outside_time_constraint

ceilometer.tests.unit.alarm.evaluator.test_threshold.TestEvaluate   

- test_no_state_change_outside_time_constraint
- test_state_change_inside_time_constraint

And this one has been failing every day for almost a week now
(starting on 7 June 2016)

ceilometer.tests.unit.test_messaging.MessagingTests.test_get_transport_optional

Is anyone looking into these?

--
Ian Cordasco

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev