summaryrefslogtreecommitdiffstats
path: root/reporting/reporting/yardstick
AgeCommit message (Collapse)AuthorFilesLines
2018-04-10Generate yardstick reporting page even if there are no datachenjiankun1-2/+1
For now, if there no data for fraser, then it will not generate the reporting page. We need to generate it even if there are no data. Change-Id: I292a1118a578ceb5e809528c68d1d88252a85c1f Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-01-10integrate daisy with yardstickSerenaFeng1-0/+1
Change-Id: I2553afdcc6515494c0a198cfa4091f1b214fe3f1 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-12bugfix: trend graph not show in fuel x86 and aarch64chenjiankun1-2/+14
The trend tool will read installer field in scenario_history.txt But now this field is fuel not fuel@x86 or fuel@aarch64. So I change fuel -> fuel@x86 & fuel@aarch64. Change-Id: I8e97e57febd559f65be559b16bceee5cf8268926 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-10-11Add fuel@x86 and fuel@arm supportchenjiankun2-104/+143
Since scenario data do not have a field named architecture, So I choose pod_name for now. For example: pod_name: arm-pod5 I assume that it is based arm architecture Change-Id: I92159a5e08b1ed80701494483fd9922dbd459193 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-09-26reporting adoption for Euphrateschenjiankun1-1/+1
Danube -> Euphrates in euphrates.html add euphrates dir fix CONFIG_REPORTING_YAML value fix import error in scenario.py Change-Id: Ic0457bf8d1c67bd21ef6a31564792eb98cfca9ad Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-09-18Add Euphrates pages for reportingMorgan Richomme1-1/+1
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-04Add vsperf in reportingMorgan Richomme1-5/+4
fix some pep8 errors in other projects Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-09Initiate packetization of Testing reportingMorgan Richomme24-0/+308
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>