Bug 10137 - oe-build-perf-test is not giving consistent metrics for build performance
Summary: oe-build-perf-test is not giving consistent metrics for build performance
Status: VERIFIED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: High major
Target Milestone: 2.2 M3
Assignee: Markus Lehtonen
QA Contact: Jose Perez C
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-08-12 15:23 UTC by Jose Perez C
Modified: 2017-04-11 20:33 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
build perf old vs new (2.22 KB, text/csv)
2016-08-12 15:23 UTC, Jose Perez C
no flags Details
Logs attached (1.75 MB, application/x-gzip)
2016-08-18 15:33 UTC, Jose Perez C
no flags Details
ubuntu logs (1.75 MB, application/x-gzip)
2016-08-18 15:53 UTC, Jose Perez C
no flags Details
logs_ubuntu_fedora (7.16 MB, application/x-gzip)
2016-08-19 13:32 UTC, Jose Perez C
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Perez C 2016-08-12 15:23:11 UTC
Created attachment 3353 [details]
build perf old vs new

The metrics that are being saved in globalres.log file by oe-build-perf-test are not being consistent, giving big differences between 2 executions, see attached log.
Comment 1 Markus Lehtonen 2016-08-15 06:51:07 UTC
Do you have logs from the tests? Seems that the tests are (mostly) failing because the elapsed time is only few minutes although it should be about an hour.
Comment 2 Jose Perez C 2016-08-15 13:22:34 UTC
Seems like the executions were successfully completed and I could not find the logs, if the execution is completed logs are saved? where are placed?
Comment 3 Jose Perez C 2016-08-18 15:33:25 UTC
Created attachment 3366 [details]
Logs attached
Comment 4 Jose Perez C 2016-08-18 15:53:52 UTC
Created attachment 3367 [details]
ubuntu logs
Comment 5 Jose Perez C 2016-08-18 15:58:25 UTC
Logs attached for ubuntu a fedora machines
Comment 6 Markus Lehtonen 2016-08-19 07:29:33 UTC
Seems that you attached the same log twice(?) I find it difficult believing that the attached log is from any of the results in the .csv file. There is no correlation between the time logs (results.log.N) and the time values in the csv.
Comment 7 Jose Perez C 2016-08-19 13:32:46 UTC
Created attachment 3370 [details]
logs_ubuntu_fedora
Comment 8 Jose Perez C 2016-08-19 13:33:25 UTC
(In reply to comment #6)
> Seems that you attached the same log twice(?) I find it difficult believing
> that the attached log is from any of the results in the .csv file. There is
> no correlation between the time logs (results.log.N) and the time values in
> the csv.

Sorry I made a mistake uploading the correct logs, I already attached the correct ones
Comment 9 Markus Lehtonen 2016-08-22 08:34:06 UTC
Now I understood the issue. The problem was that a badly broken version of the function writing globalres.log ended up in my first patchset. End result being that all correct values were there but they were basically in random order (because of usage of dict() instead of OrderedDict).

The problem should now be fixed in latest master (after 3bdb7b2e512b2f160360e95ed5b2be3871ec0b4b). Please test and re-open this bug if you still see some issues.
Comment 10 Jose Perez C 2017-04-11 20:33:15 UTC
Metrics are consistent for 2.3 M3 rc2. 

poky commit: 415b72ffcbd26e5f3664370d8b2a9b8105fb6342