summaryrefslogtreecommitdiffstats
path: root/reporting/reporting
AgeCommit message (Collapse)AuthorFilesLines
2017-10-20bug fix: score calculation based on build_tagMorgan Richomme1-3/+4
we were used to count the number of PASS of the last 4 runs it works 80% of the cases 4 runs 4 OK => 3 points 3 OK => 3 points 2 OK => 2 points 1 OK => 1 point 0 => 0 it is different from the normal score calculation 4 OK => 3 points 3 OK => 2 points 2 OK => 2 points 1 OK => 1 point 0 => 0 Change-Id: Ib8df2c294e0036246176c181b7a7ac290ebea07e Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-19Extend the Functest reporting black listMorgan Richomme1-0/+2
remove * tempest_full_parallel * rally_full Change-Id: Ibb944e7d32dc3cf0fc0b87a269c9e2f0327410e4 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-18Add new function to get indivial test score for aarch64Morgan Richomme3-7/+54
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>
2017-10-16fix yamllint verify failSerenaFeng1-0/+2
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>
2017-10-16Merge "Update table headers in the reporting page"Serena Feng1-3/+3
2017-10-12Change criteria 'SUCCESS' to 'PASS' in yardstick reportingchenjiankun1-2/+1
To keep consistent with other testing project, yardstick should change criteria value from 'SUCCESS' to 'PASS' Change-Id: I8d8779927a74749e7c43df4e55e1888c49cbbbaf Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
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-11Merge "Add fuel@x86 and fuel@arm support"Morgan Richomme3-118/+166
2017-10-11Add fuel@x86 and fuel@arm supportchenjiankun3-118/+166
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-10-07Change score calculation for functest reportingMorgan Richomme1-5/+19
the goal is not to penalize scenario with few iteration due to CI pipeline constraints until now the top score was calculated on the base on 4 iterations, it means whatever the number of iterations, we always consider the possible top score based on at least 4 iterations each case can get - 3 points (last 4 iterations PASS) - 2 points (more than 1 PASS over the last 10 days but 1 FAIL of the last 4) - 1 point (at least 1 PASS over the last 10 days) - no point (never work) so if we consider a scenario with 10 cases, the top score is 30 = 10*3 (max points) the coefficient to calculate the top score is not the number of iterations - 1 iteration => possible top score 10 - 2 iterations => top score 20 - 3 iterations => top score 20 - 4 or more iterations => top score 30 previously top score was systematically 30 https://wiki.opnfv.org/plugins/servlet/mobile#content/view/6828617 Change-Id: I01102bc00766b7f5b58e73befa7d5328fcc895cc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-03Update table headers in the reporting pageYujun Zhang1-3/+3
Change-Id: I19916f1e4dd04297cc7d73e93a12767d335c0d99 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2017-09-30Fix status reporting pageYujun Zhang3-17/+12
- 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>
2017-09-29Merge "Fix Bottlenecks status page cann't be shown."Morgan Richomme1-1/+5
2017-09-29Change Euphrates imageMorgan Richomme1-3/+3
minor pylint fix in functest/reporting-status Change-Id: Ibfd4f0da1475c34c40a3d9e00530f8f15eb3c7dc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-29Fix Bottlenecks status page cann't be shown.liyin1-1/+5
Change-Id: Ia1ad4c0654ad2dea7fdb61b81725af9aaafc4750 Signed-off-by: liyin <liyin11@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-22cloudify_ims reporting fixesMorgan Richomme4-164/+182
+ minor fixes * unknown => real test case names * pylint corrections Change-Id: I75446e4006d41fe1bb25106420910025afa01489 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-18Add Euphrates pages for reportingMorgan Richomme2-8/+2
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-07Add bottlenecks to reportingMorgan Richomme4-1/+264
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>
2017-09-04Add 2 files forgotten in previous commit for vsperf integrationMorgan Richomme2-0/+138
Change-Id: Ibfd36814ac09d16ba4b3d365e04bf3b39a1ef7db Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-04Add vsperf in reportingMorgan Richomme5-109/+280
fix some pep8 errors in other projects Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-31bug fix: reporting TempestMorgan Richomme1-42/+50
not updated since Colorado and data model changed - minor fixes to match data model - pep8/pylint correction Change-Id: I3a0a9ea689d25b3cfff35cb1ec39329981627bc6 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-28bug fix for qtip reportingMorgan Richomme2-6/+6
- fix right path (version duplicated in path) - fix template for nav links in qtip reporting page Change-Id: I7e14bea3feb5e6fad694e2837b3048b9cd8d5825 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-25Split HA and NOHA scenarios into 2 tables in reportingMorgan Richomme1-2/+27
the goal is to vizualize more quickly the HA and NOHA scenario Note that if no scenario is available, the table title is displayed Change-Id: Ibdade30aadf40fe4f7b9bfe547d23c186cb3e1df Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-16Merge "Bug fix: generate fuel reporting page when no aarch64 available"Morgan Richomme1-1/+1
2017-08-11Bug fix: generate fuel reporting page when no aarch64 availableMorgan Richomme1-1/+1
In fuel we may deal with x86 or aarch64 architecture We generate dedicated reporting page - fuel@x86 - fuel@aarch64 However when there is no results for one of the architecture the test on the number of architecture lead to a bug Change-Id: I9906bd6078c8493587dc667eb23399a1e8311e77 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-11Add daisy to reportingMorgan Richomme2-0/+2
Change-Id: I5fd940b8c1be1c327cfcd481c27049f94ae2f175 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-08-09Initiate packetization of Testing reportingMorgan Richomme69-0/+2545
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>