From a0d38d21b1108288103141b1440ca21ea8608187 Mon Sep 17 00:00:00 2001
From: Julius Pfrommer <julius.pfrommer@web.de>
Date: Sat, 7 Oct 2023 23:06:27 +0200
Subject: [PATCH] fix(build): In ci.sh use sudo for valgrind instead of
 set_capabilities

---
 tools/ci.sh | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/tools/ci.sh b/tools/ci.sh
index 2e20a77be89..b07b3ea9315 100644
--- a/tools/ci.sh
+++ b/tools/ci.sh
@@ -292,7 +292,7 @@ function unit_tests_pubsub_sks {
           -DUA_FORCE_WERROR=ON \
           ..
     make ${MAKEOPTS}
-    # set_capabilities not possible with valgrind
+    set_capabilities
     make test ARGS="-V -R sks"
 }
 
@@ -347,7 +347,7 @@ function unit_tests_valgrind {
           ..
     make ${MAKEOPTS}
     # set_capabilities not possible with valgrind
-    make test ARGS="-V"
+    sudo bash -c "make test ARGS=\"-V\""
 }
 
 ########################################
@@ -388,7 +388,8 @@ function examples_valgrind {
     # Run each example with valgrind. Wait 10 seconds and send the SIGINT
     # signal. Wait for the process to terminate and collect the exit status.
     # Abort when the exit status is non-null.
-    python3 ../tools/examples_with_valgrind.py
+    # set_capabilities not possible with valgrind
+    sudo -c "python3 ../tools/examples_with_valgrind.py"
     EXIT_CODE=$?
     if [[ $EXIT_CODE -ne 0 ]]; then
         echo "Processing failed with exit code $EXIT_CODE"