There are a bunch of tests that fail in diablo because they expect a
particular 4xx response code and that code is different in diablo and
essex. I have checked in some "fixes" for this by making the test less
rigid about which 4xx code it gets but there are still more I have to
deal with. I a
I re-ran these tests against my instance. Some of these tests could be marked
as expected failures pending a decision on what could be considered a bug or
what may not be reasonable behavior:
* The test_list_images class fails because of a 409 response (the
visibility into the exact error
Most of the errors so far have been issues with the tests themselves. I
will file bugs and/or fix them. One exception is that
test_create_image_from_deleted_server is failing. That is, an image is
being created even after delete_server is called. At the bottom of this
test there is no exception
Hi David,
Could you put the errors in http://paste.openstack.org/ for us to look
at?
Since we're about to release 2011.3.1, I'm curious whether these are
likely to be recent regressions on stable/diablo.
If they look like a recent regression, you could try using 'git bisect'
to identify which co
Just some test failures. I will track them down, but first wanted to
make sure Tempest was not intended to be Essex-only.
On 1/16/2012 2:52 PM, Daryl Walleck wrote:
Hi David,
Yes, it should be working (except for any tests failing due to bugs of course).
What types of problems are you havin
Hi David,
Yes, it should be working (except for any tests failing due to bugs of course).
What types of problems are you having?
Daryl
On Jan 16, 2012, at 1:44 PM, David Kranz wrote:
> I tried running Tempest against an existing diablo-stable cluster and had
> problems. Is this expected to wo
6 matches
Mail list logo
