Age | Commit message (Collapse) | Author | Files | Lines |
|
This change add the Gambia page to the testresults dashboard.
JIRA: RELENG-412
Change-Id: Id1ee651b9f3658adeff342c39e030dc248bf6747
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- adapt existing framework to new testcases.yaml format (dependencies)
- simplify Tier management
- unblacklist juju_epc
- add new testcases
Change-Id: I085bff327f9eca856879616215dc6bae83435e7c
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
Change-Id: Id7c95cd27332ff6c9f7d2e44738887d4ee794c70
Signed-off-by: Valentin Boucher <valentin.boucher@kontron.com>
|
|
remove
* tempest_full_parallel
* rally_full
Change-Id: Ibb944e7d32dc3cf0fc0b87a269c9e2f0327410e4
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
as architecture is not considered as a constraints (unlike scenario or
installer) we need to work on the build tag to retrieve the data
but it is not possible to use regex directly in the API
so retrieveing the accurate results require extra processing
* based on build_tag, filter the results properly per scenario
* build a table build_tag time for a given scenario
* keep only the last 4 results
* evaluation criteria field
It would simplified if architecture could be declared as a constraint
then querying the resuls will not change and not require intermediate
steps
JIRA: FUNCTEST-880
Change-Id: Id4fe4f56babf0964d41e299905c804e0d837c3d7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
fail record: https://build.opnfv.org/ci/job/opnfv-yamllint-verify-master/1050/console
Change-Id: Ic709b9a3d1d3642a3deebd930714a2ba2de22da6
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
- use data in last 10 days instead of 1 day
- hide installers without any data
- remove redundant qtip reporting
Change-Id: If73a439572b6a1cf09c7d34f643fb14be82196ca
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
very basic approach based on 1 case posca_factor_ping
Give a feedback on the CI activity of bottlenecks
Change-Id: Iaa84abac6b00ba48a771250433a9f9a068de453f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I5fd940b8c1be1c327cfcd481c27049f94ae2f175
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Testing reporting provides
- static reporting pages [1] (jinja2)
- landing pages including test case catalogue [2] (angular)
It consumes the Test API to build web pages providing status for
the testing projects (so far functest, yardstick, storperf and
qtip).
Dockerization has been initiated [3]. The goal is to replace the
static page hosted on testresults.opnfv.org by a docker regenerated
and redeployed when reporting code is changed
But the docker and more generally the testing reporting directory
must be refactored to
- manage dependencies properly
- leverage tox (py27, docs, pylint, pep8)
This patch
- setups tox (py27, pep8, pylint, docs)
- integrate the requirement management
- fix pep8 errors
- introduce 1 dummy unit test
This patch does not
- fix pylint errors
- create any doc
[1]: http://testresults.opnfv.org/reporting2/display/index.html
[2]: http://testresults.opnfv.org/reporting2/reporting/index.html
[3]: https://gerrit.opnfv.org/gerrit/#/c/36735/
Change-Id: I4613de7ca7036d6c6bbb8f58ade492b1d673599b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|