11 Jan
2022
11 Jan
'22
10:12 a.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 8500ac377be5b5cf44d536c00afa98f7a1756a98
https://github.com/tribe29/checkmk/commit/8500ac377be5b5cf44d536c00afa98f7a…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-01-11 (Tue, 11 Jan 2022)
Changed paths:
M buildscripts/infrastructure/build-nodes/centos-7/Dockerfile
M buildscripts/infrastructure/build-nodes/centos-8/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-10/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-11/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-9/Dockerfile
M buildscripts/infrastructure/build-nodes/scripts/build_lib.sh
M buildscripts/infrastructure/build-nodes/scripts/install-python.sh
A buildscripts/infrastructure/build-nodes/scripts/install-valgrind.sh
M buildscripts/infrastructure/build-nodes/sles-12sp3/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp4/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp5/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15sp1/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15sp2/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15sp3/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-16.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-18.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-19.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-20.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-21.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-21.10/Dockerfile
Log Message:
-----------
Make recent valgrind available in all CI containers
We need a valgrind in all CI Containers which is actually usable for our
needs. With older system-provided valgrinds there are a few issues:
- --error-exitcode is supported in valgrind >=3.2.0 (June 2006), so this
shouldn't be an issue with the currently supported distros. But it's
mentioned here for completeness.
- --exit-on-first_error is supported in valgrind >=3.14.0 (October
2018). This is quite handy to stop any long jobs which will fail,
anyway. And any results after the initial finding are useless, too.
- Support for the DWARF 5 debug info (generated by GCC >=11.1) is in
valgrind >=3.17 (March 2021)
- In general: We use a very recent C++-Compiler, which might emit
machine instructions older valgrinds don't understand. This could lead
to fun like this: https://bugs.kde.org/show_bug.cgi?id=353370 So we
are more or less forced to keep valgrind up-to-date, too.
CMK-9357
Change-Id: I6c4c1e4c99077a046d4ae95ec845365b7e91fdde