Remove pifpaf and dependencies to gnocchi for tox test runs.
Remove redundant gabbi tests.
Move wsme & query unit tests from fuctional to unit test folder where
they belong.
Remove integration tests which has been covered in the new tempest
cases in the depends on patch.
Remove run-tests.sh in favour of just calling stestr.
Depends-On: https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/901838
Change-Id: I5b33cba27dfcb2bbdf12c9bc6b28ecff9aa18d93
The py311 job has currently trouble locating mysqld.
On debian the mysqld binary is installed to /usr/sbin,
but on debian /usr/sbin isn't in PATH by default.
This patch appends /usr/sbin to PATH.
Change-Id: I89b2631f38e6a7292d6e58b4ddee6f7fdfc6fa9f
These were always called in series. No point to maintain the separation.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ic100f380eea90115f0a44a82d1d28d5d216bed68
This is effectively os-testr but maintained.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I97183318f715b03f31145fa3d0f00bb7bc8a0c82
new ostestr is different and is breaking gate. i don't think we
really need ostestr since we don't use it in any of the projects
under Telemetry. so to remain consistent and simple, just follow
similar pattern.
Change-Id: I742de2107cf56ef8b223fa1431529e706cc52377
Refactored run-tests script to become a setup script.
This is needed to make it work correctly with arbitary command we want
to run in venv (testenv:venv in tox).
Change-Id: I91d0e7a05fb1b9fa13e18789281fdf5267f5b526
The nova notifier is again broken due to Nova switch to oslo.messaging.
Anyway, it's likely that this code has been broken for a long time, as
it is not enabled nor tested on devstack anymore. And it's very unlikely
compatible with oslo.messaging.
This patch only disable the run of the tests for now, but we might
consider removing the code before i3 if nobody stands up and try to fix
it in a way or another.
This patch also update the configuration file for the new keystoneclient
release.
Change-Id: I679154baff476957f46e7930db69aeec7e368648
Just killing MongoDB is not enough, we also need to kill processes such
as the cat ones used to read the fifo.
Change-Id: I3fd99e333e69625e3872e24b9337cad17d46d737
On certain system, such as Darwin, the default mongod binary is a
wrapper adding a default configuration file. Let's specify that there's
no configuration file to read, otherwise a log file is used instead of
stdout.
Change-Id: I56c72cd61399405fd57d6e3f2b1f53ca6a395835
Instead of letting the tests report connection errors,
check for the mongod process early and don't run the
tests at all if it is not found.
Change-Id: Iebf420ba62954ffe0d2b9c23375c9a0ff9673845
There's actually 2 lines that matches the current rule:
[websvr] admin web console waiting for connections on port 30000
[initandlisten] waiting for connections on port 29000
Let's make it more tighten.
Related-Bug: #1218488
Change-Id: I4ba56a7c2406a9851aa8087b4cabb0aa31698763
Use 1 MongoClient instance per database server determined by host:port +
connection options
Fixes bug #1218488
Change-Id: If06844f6bf09674216b029310c1a5f445c4476fe
Because pymongo doesn't close connection on .close() when we use its
pool, we disable the MongoClient pooling feature for running tests.
This allow to use a normal number of connection in mongod for test.
Fixes bug #1218488
Change-Id: Ie4c74620937816ed0592f5ac72de99dee3173ad8
This fixed the bug #1221033 caused by the latest nova chagnes.
Temproarily enlarge the max allowed connection to mongoDB as a
workaround for bug #1218488. That bug should be addressed by
https://review.openstack.org/44465
Change-Id: I49d82bcc2c1ac6481b0f5d321db2f70549a95d55
At least on SUSE, it is not installed in /usr/bin,
which means it can not be found as normal user.
Change-Id: I636cb16429962807d9e88ba87e494ac3c7e1e5a9
This refactore storage tests to use testscenarios
The test_impl_* files now have only test related the a particular
backend.
All common tests are in test_impl_scenarios.py (previously named
base.py)
The maxconns of Mongod have been increase to allow db2 to run
Parts of blueprint db-tests-with-scenarios
Change-Id: I94955ca1cead3f7c7e04b57b9ce1313324e4a349
No prealloc should make mongod starts faster, and the while loop will
wait it is listening before running the tests.
Change-Id: Ia2ff201c0cfa882aa00bb7ce8ce990525f18339e
If 'kill -9 mongodb_pid' failed, run-tests.sh exit with a
return code of 0.
This change ensure that the return code is the one of the failed
command.
Change-Id: Iad58dac3fa66d1ea688af706940511033c1d76f7
The coverage tests mustn't run in parallel and must have a working
mongod instance like other tests.
So just use the run-tests.sh with a special flags --coverage
Fix bug #1199411
Change-Id: Id750697a69213ee753280b7adc8f726dbdb1fca5
This will allow more real tests, and use of more functionnality not
implemented in MIM such as aggregation.
Change-Id: Ie38deadf190db33863c99d4610157349484ac10f
Erno Kuvaja