Open Stack

I put a nose.cfg with my excludes in the user's root and it works to run 
nosetests via the virtual environment like this:

tempest/tools/./with_venv.sh nosetests

I had to use the run_tests.sh script in tempest to create the virtual 
environment, but after that running tempest via nose within the venv 
wasn't a problem.  Of course, I didn't want to duplicate the test runs 
when setting up the venv via run_tests.sh, so I created it with the -p 
option to only run pep8 after it was setup (I'm not aware of a way to tell 
it to not run any tests and simply setup the environment).

Going back to the bug I opened last night for failures on py26, it's fixed 
with this patch: https://review.openstack.org/#/c/39346/ 



Thanks,

MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Development

Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
E-mail: mriedem at us.ibm.com


3605 Hwy 52 N
Rochester, MN 55901-1407
United States




From:   Alexius Ludeman <lex at lexinator.com>
To:     OpenStack Development Mailing List 
<openstack-dev at lists.openstack.org>, 
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 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.  This has reduced the yum dependency 
nightmare greatly.

now that testr is default for tempest.  testr does not appear to support 
--exclusion[1] or --stop[2].

I have a work around for --exclusion, by:
testr list-tests | egrep -v regex-exclude-list > unit-tests.txt
testr --load-list unit-tests.txt

I do not have a work around for --stop.

[1]https://bugs.launchpad.net/testrepository/+bug/1208610
[2]https://bugs.launchpad.net/testrepository/+bug/1211926
[3]https://bugs.launchpad.net/tempest/+bug/1202815



On Tue, Aug 13, 2013 at 7:25 PM, Matt Riedemann <mriedem at us.ibm.com> 
wrote:
I have the same issue.  I run a subset of the tempest tests via nose on a 
RHEL 6.4 VM directly against the site-packages (not using virtualenv). 
 I'm running on x86_64, ppc64 and s390x and have different issues on all 
of them (a mix of DB2 on x86_64 and MySQL on the others, and different 
nova/cinder drivers on each).  What I had to do was just make a nose.cfg 
for each of them and throw that into ~/ for each run of the suite. 

The switch from nose to testr hasn't impacted me because I'm not using a 
venv.  However, there was a change this week that broke me on python 2.6 
and I opened this bug: 

https://bugs.launchpad.net/tempest/+bug/1212071 



Thanks, 

MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Development 

Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
E-mail: mriedem at us.ibm.com 


3605 Hwy 52 N
Rochester, MN 55901-1407
United States





From:        Ian Wienand <iwienand at redhat.com> 
To:        openstack-dev at 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 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 is preferable
to keep everything else running by skipping the problematic tests
while its being worked on.

My perspective is one of running tempest in a mixed CI environment
with RHEL, Fedora, etc.  Python 2.6 on RHEL doesn't support testr (it
doesn't do the setUpClass calls required by temptest) and nose
upstream has some quirks that make it hard to work with the tempest
test layout [2].

Having a common place in the temptest config to set these skips is
more convienent than having to deal with the multiple testing
environments.

Another proposal is to have a separate JSON file of skipped tests.  I
don't feel strongly but it does seem like another config file.

-i

[1] https://review.openstack.org/#/c/39417/
[2] https://github.com/nose-devs/nose/pull/717

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/a4dfddad/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/a4dfddad/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/a4dfddad/attachment-0001.gif>