6319 2014-05-13 13:17:51 +0000 Automated storage and graphing of build performance metrics 2017-12-06 16:48:04 +0000 1 1 10 QA/Testing Build Testing general unspecified x86 Multiple RESOLVED FIXED TRT Medium+ enhancement 2.4 M1 10582 5049 1 richard.purdie markus.lehtonen belen.barros.pena bill.randle joshuagloe konrad.scherer markus.lehtonen randy.macleod sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 43280 0 richard.purdie 2014-05-13 13:17:51 +0000 Currently, we do have various build performance numbers being run on a regular basis and we do graph those numbers for milestones. I'd like to: a) Collect this data together in a database somewhere rather than having an ever growing csv file b) Have some kind of visualisation of those numbers automatically generated like the bug trend charts. 43281 1 richard.purdie 2014-05-13 13:18:49 +0000 Adding Belen as I know there may be some overlap between some functionality of toaster and this. 50745 2 alexandru.c.georgescu 2015-05-04 13:00:04 +0000 This will be integrated in out QA REporting TOol 68687 3 benjamin.esquivel 2016-11-29 16:56:03 +0000 removing dependency to bug 9958 as it has been set to future and this bug is targeted to a specific release. 70331 4 markus.lehtonen 2017-02-01 15:17:51 +0000 Moving to milestone to 2.4 as the feature would be part of the TestReportTool. I have implemented an initial prototype web service, based on an older CustomReports project. The code is currently available in GitHub (as it is a fork from CustomReports), see build-perf branch: https://github.com/marquiz/CustomReports/tree/build-perf 72286 5 markus.lehtonen 2017-04-11 12:24:23 +0000 I'm setting the milestone now to 2.4 M1. However, I would be inclined to close the bug as fixed because test results are being automatically stored in Git and graphical test reports are being automatically sent from the testers. I'd like to see more fine-grained requirements for TRT when its design/implementation starts. 73443 6 markus.lehtonen 2017-05-23 07:49:58 +0000 Build performance test data is being automatically stored in Git: http://git.yoctoproject.org/cgit/cgit.cgi/yp-qa-build-perf-data/ Also, build performance test reports are now being automatically generated and uploaded to wiki.yoctoproject.org for each test run. Links to the latest test reports are found here: https://wiki.yoctoproject.org/wiki/Performance_Test#Daily_Test_Results Closing this bug.