According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I63079f352ff36dda4f3f64a8681431a319791f0e
This reverts commit b67c20f2db.
This change hides the LOG output from the build process in the
console.html. While the build still will succeed/fail it will not update
the log while it is running. It will only dump the output of what its
doing if it fails. This is not ideal for our gates at this time since we
have seen the even the running and successful gates sometimes do not do
what we designed the gate to do (not building the containers we want,
not running the tests we want (recently happened with bashate), etc)
Change-Id: Ida58eef41ee8874e7577fcc24174fed4808f46f1
* add a base TestCase class
* load the tests from the project root rather than only tests dir
* add a test case for WorkerThread builder function
Change-Id: Icf878f9249b475a311123c8235c42b1212d02ca6
Partially-implements: bp add-ut-codebase
1. Move setup_docker.sh to tools directory
2. Make a setup_gate.sh that installs necessary packages including
docker and starts docker.
3. Add logging output.
4. Add default test timeout of 2 hours.
5. Add user to the docker group before running test cases.
6. Run image build as dockerroot group.
This patch has to be one commit to fix the gate in one go.
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I83f3cdb1dabf0dfface589c581cb22c155467acc
This adds functional tests to tox, along with a number of prerequisite
steps. Since this is primarily a bash project, pbr usage has been avoided.
Tests are to be written in python and put in the tests directory.
Running tox -e setupenv will execute a setup script
(tests/setup_docker.sh) to ensure the running instance of docker meets
the minimum version requirement.
Running tox -e images will execute the image building script
(tools/build-all-docker-images) and will parse the resulting output to report
failures.
Running tox -e startenv will generate the environment file, run
"tools/kolla start", and run first time initialization (eventually).
Running tox -e functional is for actually testing the deployed OpenStack
environment via a series of tests utilizing the client APIs.
Change-Id: Iff6dfdca43f0c44d471e7540a7836e56a0de4507
Vu Cong Tuan