On 14:14 Thu 02 Apr , Marcus Vinícius Ramires do Nascimento wrote:
Hi Mike,
I'm working on test coverage improvement for HDS/Hitachi drivers. As I
talked to you in #openstack-cinder channel, I'm facing troubles with 3
tests (apparently those fails are not related to the driver) and I'm
We believe we have satisfied the required criteria [1] to have NetApp’s
fibre channel drivers included in the Kilo release. We have submitted a
revert patch [2] along with posting an ether pad [3] to provide more detail
on our progress. Thanks for your consideration.
[1]
Hi Mike,
I'm working on test coverage improvement for HDS/Hitachi drivers. As I
talked to you in #openstack-cinder channel, I'm facing troubles with 3
tests (apparently those fails are not related to the driver) and I'm trying
to discover if it's a bug to report it or if it's a
Hi Mike,
The majority of the CIs don't run all 304 tests mostly because of these
tempest problems. I remember there was a list in the Thirdparty CI Wiki
with the common tests that used to fails to everyone, or at least most of
people. IMO its better to have a more consistent CI than CIs with
On 09:39 Thu 26 Mar , Mike Perez wrote:
As discussed in the last Cinder meeting [1], in order to have your volume
driver readded into the Kilo release, you must have a CI reporting and stable
for five days prior to 4/6.
This includes:
1) Providing logs to screen sessions, etc configs,
On 14:38 Thu 26 Mar , Erlon Cruz wrote:
snip
Our HBSD drivers are only running 211 because we remove the snapshots tests
that were failing due a patch that broken our driver.
Whats being done about that in Kilo? That's a minimum feature required for all
drivers in Cinder:
Hi Mike,
I'm working on it! The bug was fixed and now I'm working to get all
tempest.api.volume tests back again on our CI, including also the tests
that were missing.
On Thu, Mar 26, 2015 at 3:00 PM, Mike Perez thin...@gmail.com wrote:
On 14:38 Thu 26 Mar , Erlon Cruz wrote:
snip
Our
Thanks Mike. The wiki still showing the old edit when I had sent out my earlier
email but I see it's been updated now. I've tested running with tox -e all --
volume and that gets us to 291 tests now.
-Ryan
On Mar 26, 2015, at 4:28 PM, Mike Perez thin...@gmail.com wrote:
On 21:45 Thu 26 Mar
Rightfully so, but it doesn't hurt to offer suggestions that might improve the
community. It would just be nice to have exclusions reconsidered if there are
legitimate bugs behind them. You see them all the time in the tempest tests ala
SKIPPED: Skipped until Bug: 1373513 is resolved so it's
On 00:11 Fri 27 Mar , Ryan Hsu wrote:
Thanks Mike. The wiki still showing the old edit when I had sent out my
earlier email but I see it's been updated now. I've tested running with tox
-e all -- volume and that gets us to 291 tests now.
Ah gotcha. That's great to hear, thank you!
--
On 00:24 Fri 27 Mar , Ryan Hsu wrote:
Rightfully so, but it doesn't hurt to offer suggestions that might improve
the community. It would just be nice to have exclusions reconsidered if there
are legitimate bugs behind them. You see them all the time in the tempest
tests ala SKIPPED:
Mike,
I am communicating this problem with my teams and will get it resolved asap.
Jay
On Mar 26, 2015 1:23 PM, Mike Perez thin...@gmail.com wrote:
On 09:39 Thu 26 Mar , Mike Perez wrote:
As discussed in the last Cinder meeting [1], in order to have your volume
driver readded into the
Thanks for clarifying!
Ryan
On Mar 26, 2015, at 5:29 PM, Mike Perez thin...@gmail.com wrote:
On 00:24 Fri 27 Mar , Ryan Hsu wrote:
Rightfully so, but it doesn't hurt to offer suggestions that might improve
the community. It would just be nice to have exclusions reconsidered if there
are
You want to run the volume tests and not tempest.api.volume tests.
-Original Message-
From: Ryan Hsu [mailto:r...@vmware.com]
Sent: Thursday, March 26, 2015 3:50 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] Deadline For Volume
Hi Mike,
We (VMware CI) run testr run tempest.api.volume for our Cinder CI and this
runs about ~240 tests for us. I'm guessing that the rest of the ~60 tests are
not being run due to skips and disabled features. For example, here is a
sampling of tests that are skipped in a recent run (note
On 21:45 Thu 26 Mar , Ryan Hsu wrote:
Hmm, that's what I thought at first but when I looked at the What tests do
I use FAQ, the tests that it says to use links to:
http://git.openstack.org/cgit/openstack/tempest/tree/tempest/api/volume,
which is exactly what we're running. Even so, I ran
On 03/26/2015 06:48 PM, Ryan Hsu wrote:
Exclusions are legitimate and will always be necessary at some point. In the
case of the linked bug, this was once a known issue for the VMware driver and
we had excluded affected tests so that CI could continue to run. This is the
same way we do it
Exclusions are legitimate and will always be necessary at some point. In the
case of the linked bug, this was once a known issue for the VMware driver and
we had excluded affected tests so that CI could continue to run. This is the
same way we do it in Nova CI and oslo.vmware CI.
Thanks,
Ryan
On 22:42 Thu 26 Mar , Ryan Hsu wrote:
Like I mentioned earlier, these numbers are going to be different for
everyone depending on their testbed set up or driver capabilities. Just by
disabling Heat in devstack you're going to miss some tests. As long as people
are transparent about this, I
19 matches
Mail list logo
