Compiling with ASan will completely distort the VmPeak memory usage
statistics the benchmark provides, and it is incompatible with Valgrind.
In addition, the timing statistics with either sanitizer will be
distorted too. So exit immediately if compiled with either.

Reported-at: 
https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/
Fixes: f4a66b7871d6 ("tutorial: Add developer performance benchmark.")
Signed-off-by: Rosemarie O'Riorden <[email protected]>
---
 tutorial/ovn-benchmark.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tutorial/ovn-benchmark.sh b/tutorial/ovn-benchmark.sh
index 01c090e84..9de23be1d 100755
--- a/tutorial/ovn-benchmark.sh
+++ b/tutorial/ovn-benchmark.sh
@@ -161,6 +161,11 @@ if [ ! -d "$PWD/sandbox" ]; then
     exit 1
 fi
 
+if [ "$(nm -an $PWD/../controller/ovn-controller | grep "asan\|ubsan")" ]; then
+    echo "Compiled with address sanitizer, which is incompatible. Exiting."
+    exit 1
+fi
+
 # Apply defaults if not set by user.
 NODES=${NODES:-$DEFAULT_NODES}
 
-- 
2.56.0

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to