| commit | b610eba335d5c8ac7484dbb1c886b125e2dea058 | |
| author | Thomas Huth <thuth@redhat.com> | |
| Wed, 15 Jul 2020 04:32:48 +0000 (15 06:32 +0200) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Fri, 17 Jul 2020 08:44:23 +0000 (17 10:44 +0200) | ||
| tree | 11925ff10dd2ec9af14daea29793f3d97b13afbe | treesnapshot (tar.gz zip) |
| parent | ab2d185d6b1d3aa1ab2416a896347d235e32ac3d | commitdiff |
gitlab-ci.yml: Add fuzzer tests
So far we neither compile-tested nor run any of the new fuzzers in our CI,
which led to some build failures of the fuzzer code in the past weeks.
To avoid this problem, add a job to compile the fuzzer code and run some
loops (which likely don't find any new bugs via fuzzing, but at least we
know that the code can still be run).
A nice side-effect of this test is that the leak tests are enabled here,
so we should now notice some of the memory leaks in our code base earlier.
Message-Id: <20200716100950.27396-1-thuth@redhat.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
So far we neither compile-tested nor run any of the new fuzzers in our CI,
which led to some build failures of the fuzzer code in the past weeks.
To avoid this problem, add a job to compile the fuzzer code and run some
loops (which likely don't find any new bugs via fuzzing, but at least we
know that the code can still be run).
A nice side-effect of this test is that the leak tests are enabled here,
so we should now notice some of the memory leaks in our code base earlier.
Message-Id: <20200716100950.27396-1-thuth@redhat.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| .gitlab-ci.yml | diffblobblamehistory |