For some reason, when Tobiko retries many times ssh connection
and logs a lot of data in the log file, pytest may fail with
"Too many open files" exception raised.
To avoid that lets try to configure soft ulimit for opened files
to be as high as possible (same as hard limit).
Change-Id: I6fb8977d7909798a5ab6be499044cc74ac34dfa2
It seems that without that option our docs builds on readthedocs
are failing now. Git advices there to use "--always" option so lets
try that.
Change-Id: I90ccccb51e46353495e6cc42547a30b842d90805
- Remove support for constrains file from infrared plugin
- Use file stored on tobiko repository by default
Change-Id: I0f835d753fb9d3a1670e8eb9b196e02e989d4262
This allows to import old varlink based podman client
ase podman1 while keeping safe to install the new
client podman-py package as podman.
To archive such result it first temporarly rename existing podman
dir, then install podman package on its place, renames it as
podman1, and finally restore pre-existing podman directory
if any initially found.
Change-Id: If834cc383f11e656f17e49d5e6fa401ac8bee829
- Set workflow step name as junit test suite name
- Set HTML report title
- Render HTML report all test case rows collapsed
- Add tobiko release version and Git commit to
reported environment metadata
Change-Id: Id827146d1f8455047dd5eedfa90171da8be02ea5
- Pass linters and lower-constrains jobs with Python 3.8
- Use master version of pylint only with python version >= 3.9
- Update requirements files
- Fix install_bindeps.sh
- Disable running DevStack jobs on ubuntu focal nodes
Change-Id: Ie745fe5b5a08fe088fcf39edb312170c6cbdc5bb
Add new env variable to handle test cases
execution when debugging test cases under a
debugger by using testools.run runner.
Change-Id: Ia6ec38e6471d93dd98c3fef17e66e9187c666c9d
- Dockerfile file is intended for running test cases
without using tox
- infrared_plugin/Dockerfile file is intended to run
Tobiko IR plugin
- docker-compose file is intended to emulate the tox
experience by using docker
All images are build staring from official CentOS 8
image.
Change-Id: I2f57f6e1c9c6161cef9448d25027d784ebd37e2c
Tox venv commands are expected to return a code that indicates
test cases final outcome:
- 0 => any test vase has failed
- 1 => some test case has failed
- not in [0, 1] => any other error
This change handles the special case when some test cases have
failed. In any of below cases:
- JENKINS_URL environment variable is defined on controller node
- --ignore-test-failure flag is passed to IR plugin
then the plugin runs without treating it as an error.
This has been introduced because when running the plugin from
a Jenkins slave host, Jenkins itself is expected to check test
case have failed looking at produced Junit XML artifacts.
Change-Id: Ia7d7f736ae18a7561dced2271228d86ca658e892
- Acreate a new tools/run_tests.py script to
execute test cases
- Move report generation to such script and
remove 'report' tox environment
- Running test cases generates report files
(.log, .html, .xml) into 'report/{envname}'
directory
- Test cases failures will returns exit code 1
Other script test runner failures returns
exit code 2
Big refactory to tox.ini file to try semplifying it:
- create the new 'py3' tox environment for running unit
tests as default platform python 3 interpreter
- use same as py3 '{envdir}' for scenario, functional,
neutron and faults tox environments
Change-Id: Id09425245cc86b84b41e6b3b1c1db759cc686f3a
seeder option is in the newest virtualenv only ,
and under this condition, virtualenv will never upgrade :
[stack@undercloud-0 tobiko]$ if ! python3 -m virtualenv --version; then
> virtualenv --version;fi
16.0.0
Change-Id: I86c5bf6429a5ae67b049fb88564ff7b7ef72968c
