Unit tests timed out: Build timed out (after 50 minutes). Marking the build as failed.

Bug #1371738 reported by Vish Ishaya on 2014-09-19
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned

Bug Description

There was an apparent hang that hit the unit tests:

2014-09-19 03:47:46.171 | {3} nova.tests.volume.test_cinder.CinderApiTestCase.test_unreserve_volume [0.006287s] ... ok
2014-09-19 03:47:46.710 | Exception TypeError: "'NoneType' object is not callable" in <bound method GreenSocket.__del__ of <eventlet.greenio.GreenSocket object at 0xf77ee50>> ignored
2014-09-19 04:39:36.440 | Build timed out (after 70 minutes). Marking the build as failed.

The error message could be a red herring because it was ignored, but something made the tests stop running.

Sean Dague (sdague) wrote :

Hey Vish, with just this amount of content it's not really possible to figure out what to do next. Can you minimally link to the logs in question.

Changed in nova:
status: New → Incomplete
Vish Ishaya (vishvananda) wrote :

Pretty sure the Greensocket was a red herring. But I've seen more timeouts like here:

http://logs.openstack.org/63/121663/3/check/gate-nova-python27/b717fe2/console.html

Changed in nova:
status: Incomplete → New
summary: - Eventlet hang in unit tests: 'NoneType' object is not callable" in
- <bound method GreenSocket.__del__ of <eventlet.greenio.GreenSocket
- object at 0xf77ee50>>
+ Unit tests timed out: Build timed out (after 50 minutes). Marking the
+ build as failed.
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers