[openstack-dev] Building on Debian: Havana unit tests at build time report

Thomas Goirand zigo at debian.org
Thu Oct 17 15:17:46 UTC 2013


Hi,

Thanks a lot Monty, for your valuable comments. Below is the list of
bugs I submitted in Launchpad (plus a few comments).

Cheers,

Thomas Goirand (zigo)

On 10/17/2013 09:08 PM, Monty Taylor wrote:
>> * Ceilometer
>> ============
>>
>> No failure, except for calling binaries which are not installed (yet) at
>> package build time, called by subprocess.py. Example:
>>
>> FAIL: tests.test_bin.BinTestCase.test_run_expirer
>> tags: worker-0
>> ----------------------------------------------------------------------
>> Empty attachments:
>>   pythonlogging:''
>>
>> Traceback (most recent call last):
>>   File
>> "/home/zigo/sources/openstack/havana/ceilometer/build-area/ceilometer-2013.2~rc2/tests/test_bin.py",
>> line 45, in test_run_expirer
>>     "--config-file=%s" % self.tempfile])
>>   File "/usr/lib/python2.7/subprocess.py", line 709, in __init__
>>     errread, errwrite)
>>   File "/usr/lib/python2.7/subprocess.py", line 1326, in _execute_child
>>     raise child_exception
>> OSError: [Errno 2] No such file or directory
>>
>> Same result under Wheezy backports and Sid.
>>
>> In Quantum/Neutron, this has been fixed, but I can't remember how. Could
>> anyone tell? It'd be great if it could be fixed.
> 
> Def should be a bug.

https://bugs.launchpad.net/ceilometer/+bug/1237420

>> Note that I already uploaded python-wsme 0.5b6 which is needed by the
>> last RC of Ceilometer, so we are fine on this ground.
> 
> There is a bug here too. You say that Ceilometer needs 0.5b6 - but
> global-requirements.txt only lists 0.5b5. We should fix that.
> 
> Additionally, I believe we need to stop depending on betas of things
> that aren't participating in the gate.

I've uploaded 0.5b6 because of:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725652

Thinking about it again, I don't think that Ceilometer needs that
version, though I did need to fix this bug...

>> * Horizon
>> =========
>>
>> Under Sid, sometimes the unit tests are passing without an issue, and
>> *sometimes* there's a timeout with Selenium that produces errors:
>>
>> ERROR: test suite for <class
>> 'openstack_dashboard.dashboards.admin.users.tests.SeleniumTests'>
>> ----------------------------------------------------------------------
>>
>> [ ... ]
>>
>>   File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line
>> 984, in shutdown
>>     "Failed to shutdown the live test server in 2 seconds. The "
>> RuntimeError: Failed to shutdown the live test server in 2 seconds. The
>> server might be stuck or generating a slow response.
>>
>> ERROR: test suite for <class
>> 'openstack_dashboard.test.tests.selenium.BrowserTests'>
>> ----------------------------------------------------------------------
>>
>> [ ... ]
>>
>>     raise cls.server_thread.error
>> WSGIServerException: [Errno 98] Address already in use
> 
> Sounds like a bug.

https://bugs.launchpad.net/horizon/+bug/1241027

>> Also, Horizon insist on a requirement on python-coverage wrapper in
>> /usr/bin/coverage:
>>
>> Running Horizon application tests
>> ./run_tests.sh: line 301: coverage: command not found
>> ./run_tests.sh: line 302: coverage: command not found
>> Running openstack_dashboard tests
>> ./run_tests.sh: line 311: coverage: command not found
>> Tests failed.
> 
> run_tests.sh is not supported. However, I'm not 100% confident that
> we've got horizon up to date on everything- so I think this could count
> as a bug.

So what's the way to run Horizon unit tests?

>> * Keystone
>> ==========
>>
>> Under Sid, I have a single unit test failure:
>>
>> FAIL:
>> keystone.tests.test_wsgi.LocalizedResponseTest.test_static_translated_string_is_Message

https://bugs.launchpad.net/keystone/+bug/1241030

>> And in Wheezy, what's below:
>>
>> ERROR:
>> keystone.tests.test_wsgi.LocalizedResponseTest.test_static_translated_string_is_Message

https://bugs.launchpad.net/keystone/+bug/1241032

> Sounds lke maybe TWO bugs! :)

So, as per your advice, I filled 2 separate bug reports.

>> * Neutron
>> =========
>>
>> Only 2 failures which don't seem so important under Sid:
>>
>> FAIL: process-returncode
>> process-returncode
>> ----------------------------------------------------------------------
>> _StringException: Binary content:
>>   traceback (test/plain; charset="utf8")
>>
>>
>> ======================================================================
>> FAIL:
>> neutron.tests.unit.ml2.drivers.test_cisco_mech.TestCiscoBasicGet.test_single_get_admin
>> neutron.tests.unit.ml2.drivers.test_cisco_mech.TestCiscoBasicGet.test_single_get_admin
>> ----------------------------------------------------------------------
>> _StringException
>>
>>
>> These appear in both Sid and Wheezy backports.

Could anyone comment on this one?

>> * Nova
>> ======
>>
>> Only a single: FAIL:
>> nova.tests.db.test_migrations.TestNovaMigrations.test_walk_versions in
>> Sid. The relevant part is:
>>
>> OperationalError: (OperationalError) table instances has no column named
>> cleaned u'CREATE INDEX instances_host_deleted_cleaned_idx ON instances
>> (host, deleted, cleaned)' ()
>>
>> It would really be nice if that one could be fixed, and that's the
>> failure which worries me the most. Note that this is using sqlite3.
>> There's no error at all under Wheezy backport, which leads me to believe
>> the error is linked to SQLAlchemy 0.8.2 in Sid.
> 
> Yes. As Robert pointed out, we don't support that yet. BUT - as I said,
> I highly support us upgrading to 0.8 now that icehouse is underway.
> Perhaps a bug?

https://bugs.launchpad.net/nova/+bug/1241038




More information about the OpenStack-dev mailing list