From fff1982359b1d2ef9b9d9106178768dd91d5b31e Mon Sep 17 00:00:00 2001 From: DURAND Malo Date: Thu, 2 May 2024 04:27:03 +0200 Subject: [PATCH] adding LEAK SUMMARY --- .github/workflows/ci.yml | 2 ++ README.md | 3 +-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index f4a9bb2..ece4986 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -153,6 +153,8 @@ jobs: block="${line}" elif [[ $(echo "${line}" | grep '^==.*== Open file descriptor .*: .*$') ]]; then block="${line}" + elif [[ $(echo "${line}" | grep '^==.*== LEAK SUMMARY:.*$') ]]; then + block="${line}" fi done < ${{ env.VALGRIND_REPORTS }} exit "${status}" diff --git a/README.md b/README.md index 1ba574b..612b79c 100644 --- a/README.md +++ b/README.md @@ -111,9 +111,8 @@ If you have write your unit tests correctly, and have the most coverage possible, then the valgrind tests will make sure that the code you wrote, both the tests and the actual implementations, are not leaking at all. Valgrind will look for : -- unfree'd memory, +- memory leaks (including inside `fork()` children), - unclosed file descriptor, -- bad memory management inside `fork()` children, - invalid read/writes, - conditionnal jumps or move depends on uninitialised value(s)