Makes those files conformant with current linting rules and avoids
linting errors when we need to toch them again.
Previous doing "pre-commit run -a" uncovered these errors, now is no
longer reporting any other errors.
Change-Id: Ie4cf229c8f11c2b55b323eac23c89483b26d3781
This is a better way to install and run stackviz, also removing some
tasks that's no longer necessary:
* Remove stackviz static files from the repo, since it's already in the
tarball
* Remove stackviz cloning, and using tarball
* Install stackviz directly from pip module
* Removing tempest-status.yml since we don't use to anything
* Move tempest-results.yml to run before stackviz, so we can take
advantage of the testrepository.subunit file to generate stackviz data
* Use testrepository.subunit to generate subunit2html report instead
of stestr/testr stream
Closes-Bug: 1779562
Change-Id: I918e5401b4f46e947bbaca99a48c2b21bce9a4bd
* Introduced new workflow for validate-tempest role
- Remove previously created tempest artifacts
- Install tempest
- Create tempest workspace
- Create tempest resources
- Generate tempest configurations
- Run tempest
- Removed unused ironic undercloud fake services
- Removing public network from undercloud as there is no public network
- Added tempest_dir var to give path to tempest workspace
- use {{ working_dir }}/tempest_git for clonning stuff
- Added test_black_regex to skip a series of tests
- Fixed permission issue for tempest_dir to generate subunit files
- Install stestr subunit-filters and subunit for generating subunit files
- Added tempest_skip_master containing skip list for undercloud
- Introduced tempest_conf_version for installing particular version of
tempestconf from git
- Enable set -e to find the exit status of command running inside
container
Change-Id: I021432e222fae0e57a13ca4859ba77e990ac6c67
The workflow of
- configure_tempest is only defined twice and used in an important
condition but it is not really used anywhere; the variable which is
around is tempest_config. Use tempest_config properly, remove
then configure_tempest;
- execute validate-tempest also when tempest_config is true,
not only when run_tempest is true;
- execute the post-tempest task only if run_tempest is true;
no need to execute it if tempest was simply configured.
Change-Id: I84dce8ff4ebb1df2163b1de6279b35e564efea5b
If run_tempest is True the tempest should be configured before,
so no need to specify tempest_config separately for this.
Change-Id: I1527c1b689d46abe89c02bed19a60a57eb9dbe07
Stackviz wasn't being executed when tempest have a failure, because
post-tempest exits with tempest status code. So, once tempest fails,
stackviz is not executed, not generating the report.
Change-Id: Ia87eb11bc7d0d2cae4eb76481d446a63671a99e8
This patch add to tempest role, the generation of the report created by
stackviz from tempest results. Basically, what it does is:
- Download stackviz from git repository
- Copy static html and javascript stackviz files so we don't need
to install npm, download the dependences, and build the static html
(which would save some minutes)
- Install stackviz (only the processor)
- Run stackviz-export on tempest to collect the results
Also, add the code needed in the collect logs role to collect these
static files generated by stackviz.
Change-Id: Ia5ee717eaa9777bad265ecc338154e131021283f
Ghanshyam Mann