openstack
/
charm-pacemaker-remote
Code Issues Proposed changes

Retarget Zaza to master now that split has landed 

This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again

Change-Id: Ie81cd20869274b5428cc58c21b91463ea3c6eee3
This commit is contained in:
Chris MacNaughton 2019-05-22 12:25:56 +02:00
parent 29e29976e4
commit 8223b8eda0
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/test-requirements.txt
View File

@ -1,3 +1,3 @@
# zaza
git+https://github.com/openstack-charmers/zaza.git@remove-namespaced-tests#egg=zaza
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack

2
src/tests/tests.yaml
View File

@ -2,7 +2,7 @@ charm_name: pacemaker-remote
tests:
- zaza.openstack.charm_tests.pacemaker_remote.tests.PacemakerRemoteTest
configure:
- zaza.openstack.charm_tests.noop.setup.basic_setup
- zaza.charm_tests.noop.setup.basic_setup
gate_bundles:
- basic
smoke_bundles: