tmp

tarantool · Nov 29, 2024 · 1f34ef5 · 1f34ef5
1 parent 627552e
commit 1f34ef5
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/.github/workflows/valgrind-testing.yaml b/.github/workflows/valgrind-testing.yaml
@@ -44,17 +44,17 @@ jobs:
           - BUILDTYPE: Release
             CMAKEFLAGS: -DCMAKE_BUILD_TYPE=RelWithDebInfo
           - VALGRIND_SCENARIO: full
-            VALGRIND_OPTS: --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose
+            VALGRIND_OPTS: --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --error-exitcode=1
             JOB_POSTFIX: "leak-check: full"
           # The use of `0x00` and `0xFF` for memory fill helps to detect dirty
           #  reads. `0x00` mimics zero-initialized memory, which can mask some
           #  uninitialized memory usage. `0xFF` fills memory with a non-zero
           #  values to make such errors easier to spot.
           - VALGRIND_SCENARIO: malloc-free-fill-0x00
-            VALGRIND_OPTS: --leak-check=no --malloc-fill=0x00 --free-fill=0x00 --verbose
+            VALGRIND_OPTS: --leak-check=no --malloc-fill=0x00 --free-fill=0x00 --verbose --error-exitcode=1
             JOB_POSTFIX: "malloc/free-fill: 0x00"
           - VALGRIND_SCENARIO: malloc-free-fill-0xff
-            VALGRIND_OPTS: --leak-check=no --malloc-fill=0xff --free-fill=0xff --verbose
+            VALGRIND_OPTS: --leak-check=no --malloc-fill=0xff --free-fill=0xff --verbose --error-exitcode=1
             JOB_POSTFIX: "malloc/free-fill: 0xff"
     runs-on: [self-hosted, regular, Linux, x86_64]
     name: >