stackforge/puppet-openstack_dev_env
Code Issues Proposed changes

explicitly exit from tests

Browse Source 
this commit adds an explicit exit from the tempest tests.

Sometimes vagrant's ssh command does not return, this explicit exit
appears to guarentee that it exits.
This commit is contained in:
Dan Bode
2013-04-02 10:13:29 -07:00
committed by Dan Bode
parent 7f025fd164
commit 7f512e2a2b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
test_scripts/openstack_test.sh
View File

@@ -71,9 +71,9 @@ elif [ $test_mode = 'tempest_smoke' ]; then
# run the tempest smoke tests
bundle exec vagrant ssh -c 'sudo puppet apply --certname tempest --modulepath=/etc/puppet/modules-0/ /etc/puppet/manifests/site.pp --trace --debug' openstack_controller
# run tempest tests
bundle exec vagrant ssh -c 'cd /var/lib/tempest/;sudo ./jenkins_launch_script.sh --smoke;' openstack_controller
bundle exec vagrant ssh -c 'cd /var/lib/tempest/;sudo ./jenkins_launch_script.sh --smoke;exit $?;' openstack_controller
elif [ $test_mode = 'tempest_full' ]; then
bundle exec vagrant ssh -c 'cd /var/lib/tempest/;sudo ./jenkins_launch_script.sh;' openstack_controller
bundle exec vagrant ssh -c 'cd /var/lib/tempest/;sudo ./jenkins_launch_script.sh;exit $?;' openstack_controller
elif [ $test_mode = 'unit' ]; then
bundle exec rake test:unit
else