benchtests: keep comparing even if function timings do not match

Allows other functions to be processed, making the script a bit more fault
tolerant thus useful.

	* benchtests/scripts/compare_bench.py (compare_runs): Continue instead of return.

diff --git a/ChangeLog b/ChangeLog
index f85b3f5fd99b15aa9a3866006447a5a1d5a57ca4..18b9f37637f9869680cc78e8b1557d1ab0caf874 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2018-12-12  Leonardo Sandoval  <leonardo.sandoval.gonzalez@intel.com>
+
+       * benchtests/scripts/compare_bench.py (compare_runs): Continue
+       instead of return.
+
 2018-12-12  Florian Weimer  <fweimer@redhat.com>
 
        * sysdeps/posix/timespec_get.c: Add missing “any later version”

diff --git a/benchtests/scripts/compare_bench.py b/benchtests/scripts/compare_bench.py
index f4b7742f90338e02235363cb955781765e6840ed..9cbbda6be627998dd9f82a0ad31550455c31d314 100755 (executable)
--- a/benchtests/scripts/compare_bench.py
+++ b/benchtests/scripts/compare_bench.py
@@ -77,7 +77,7 @@ def compare_runs(pts1, pts2, threshold):
             # timing info for the function variant.
             if 'timings' not in pts1['functions'][func][var].keys() or \
                 'timings' not in pts2['functions'][func][var].keys():
-                    return
+                    continue
 
             # If two lists do not have the same length then it is likely that
             # the performance characteristics of the function have changed.