Re: [openstack-dev] Skipping tests in tempest via config file

2013-08-14 Thread Robert Collins
On 14 August 2013 14:10, Ian Wienand wrote: > Hi, > > I proposed a change to tempest that skips tests based on a config file > directive [1]. Reviews were inconclusive and it was requested the > idea be discussed more widely. > > Of course issues should go upstream first. However, sometimes test

Re: [openstack-dev] Skipping tests in tempest via config file

2013-08-14 Thread Robert Collins
On 15 August 2013 04:35, Alexius Ludeman wrote: > I am running tempest on OEL 6.3 (aka RHEL 6.3) and I had issues with > python 2.6 and skipException[3], so now I'm using python 2.7 just for > tempest. I also had difficulty with yum and python module dependency and > made the transition to venv.

Re: [openstack-dev] Skipping tests in tempest via config file

2013-08-14 Thread Matt Riedemann
mrie...@us.ibm.com 3605 Hwy 52 N Rochester, MN 55901-1407 United States From: Alexius Ludeman To: OpenStack Development Mailing List , Date: 08/14/2013 11:39 AM Subject: Re: [openstack-dev] Skipping tests in tempest via config file I am running tempest on OEL 6.3 (aka R

Re: [openstack-dev] Skipping tests in tempest via config file

2013-08-14 Thread Alexius Ludeman
2 | *Mobile:* 1-507-990-1889* > E-mail:* *mrie...@us.ibm.com* > [image: IBM] > > 3605 Hwy 52 N > Rochester, MN 55901-1407 > United States > > > > > > From: Ian Wienand > To: openstack-dev@lists.openstack.org, > Date:08/13/2013 09:13 PM

Re: [openstack-dev] Skipping tests in tempest via config file

2013-08-13 Thread Matt Riedemann
From: Ian Wienand To: openstack-dev@lists.openstack.org, Date: 08/13/2013 09:13 PM Subject: [openstack-dev] Skipping tests in tempest via config file Hi, I proposed a change to tempest that skips tests based on a config file directive [1]. Reviews were inconclusive and it wa

[openstack-dev] Skipping tests in tempest via config file

2013-08-13 Thread Ian Wienand
Hi, I proposed a change to tempest that skips tests based on a config file directive [1]. Reviews were inconclusive and it was requested the idea be discussed more widely. Of course issues should go upstream first. However, sometimes test failures are triaged to a local/platform problem and it