This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
[PATCH v2 1/3] benchtests: keep comparing even if function timings do not match
- From: leonardo dot sandoval dot gonzalez at linux dot intel dot com
- To: libc-alpha at sourceware dot org
- Cc: Leonardo Sandoval <leonardo dot sandoval dot gonzalez at linux dot intel dot com>
- Date: Tue, 11 Dec 2018 16:46:57 -0600
- Subject: [PATCH v2 1/3] benchtests: keep comparing even if function timings do not match
- References: <20181211224659.29876-1-leonardo.sandoval.gonzalez@linux.intel.com>
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
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.
---
benchtests/scripts/compare_bench.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/benchtests/scripts/compare_bench.py b/benchtests/scripts/compare_bench.py
index f4b7742f90..9cbbda6be6 100755
--- 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.
--
2.19.2