Thanks Morgan . I’m clear about that now.
Regards, Kubi 发件人: [email protected] [mailto:[email protected]] 发送时间: 2017年8月28日 15:47 收件人: Gaoliang (kubi) <[email protected]> 抄送: [email protected]; Lvjing (Jing Lu) <[email protected]>; [email protected]; [email protected] 主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report??? the trend line can cover a long period, it is based on the local file storing all the results but a trend line is associated with a scenario and the list of scenarios is built based on the results over the last 10 days that is why if there is no run since 10 days, we have an empty page In deed we have fortunately results for all the installers [morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep compass |wc -L 57 [morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep fuel |wc -L 63 [morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep apex |wc -L 53 [morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep joid |wc -L 54 but last run on - compass: 28/8 - fuel: 11/8 - apex: 20/5 - joid: 3/8 The reporting page really reflects the CI activity, we could amend the reporting to consider all the scenarios stored in the local file rather than considering the scneario over the last 10 days...but empty pages mean something (no CI activity) In Euphrates we introduced the scenario in the test API. It is not used yet but it should replace the local file /Morgan On 28/08/2017 09:33, Gaoliang (kubi) wrote: "In functest we save the status after each release (Danube 1.0, Danube2.0, Danube 3.0) in our repo" That's a best practice for reporting. We should followed that at E release :) By the way, Is it possible to show the Trend picture even if there is no data in last 10 days. we may don't need to see the score and status which are calculated by last 10 day's result but a trend from one or two month result for each scenario. Such as compass page, we can see the trend from April to August http://testresults.opnfv.org/reporting/yardstick/release/danube/index-status-compass.html Regards, Kubi -----邮件原件----- 发件人: [email protected]<mailto:[email protected]> [mailto:[email protected]] 代表 [email protected]<mailto:[email protected]> 发送时间: 2017年8月28日 14:47 收件人: [email protected]<mailto:[email protected]>; Lvjing (Jing Lu) <[email protected]><mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report??? regarding the reporting link, it always deals with a sliding windows processing the results from the last 10 days if no results since 10 days for the given version => no results so currently no Danube results, some runs on master => http://testresults.opnfv.org/reporting/yardstick/release/master/index-status-fuel.html In functest we save the status after each release (Danube 1.0, Danube2.0, Danube 3.0) in our repo it is possible to rebuild the status assuming that we save the scores in a local files but it will be just a "release status" and it will not be as detailed as the first link you mentioned. /Morgan On 26/08/2017 09:46, [email protected]<mailto:[email protected]> wrote: And on the other hand, If I go to the below link it is showing empty, How can I get the result of each Yardstick result performnace numbers . Please help http://testresults.opnfv.org/reporting/yardstick/release/danube/index- status-fuel.html _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ opnfv-tech-discuss mailing list [email protected]<mailto:[email protected]> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss -- Morgan Richomme Orange/ IMT/ OLN/ CNC/ NCA/ SINA Network architect for innovative services Future of the Network community member Open source Orange community manager tel. +33 (0) 296 072 106 mob. +33 (0) 637 753 326 [email protected]<mailto:[email protected]> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
