, 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 the tox -e all
hard to understand
why we can't just apply the same principles to third-party CI.
Thanks,
Ryan
On Mar 26, 2015, at 4:42 PM, Anita Kuno ante...@anteaya.info wrote:
On 03/26/2015 06:48 PM, Ryan Hsu wrote:
Exclusions are legitimate and will always be necessary at some point. In the
case
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
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 Mar 26, 2015, at 3:30 PM, Mike Perez thin...@gmail.com wrote:
On 20:49 Thu 26 Mar , Ryan Hsu wrote:
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
Hi All,
There was a change [1] 2 days ago in django-openstack-auth that introduces a
new requirement oslo.config=1.6.0 to the project, which is now present in the
1.1.9 release of django-openstack-auth. While this change is in sync with
master requirements, oslo.config=1.6.0, it does not jive
Thanks very much Jeremy for getting us back up and running again. Without a
doubt, we will be triggering directly from the CI system itself next time the
need to do a mass recheck arises. The lesson was learned seconds after the
script was run!
Again, my sincere apologies for all the havoc
Also, I have added a section noting crucial bugs/patches that are blocking
Minesweeper.
Ryan
On Feb 5, 2014, at 2:03 PM, Shawn Hartsock harts...@acm.org wrote:
FYI:
We're keeping usage notes on VMware Minesweeper here:
Did you mean flags as in excluding tests? We have an exclude list but these
bugs are intermittent problems that can affect tests at random.
On Feb 5, 2014, at 4:18 PM, John Dickinson m...@not.mn wrote:
On Feb 5, 2014, at 4:04 PM, Ryan Hsu r...@vmware.com wrote:
Also, I have added
