echo "NEWSX" | hunspell -a with and w/o valgrind differed in
lower case. This could be workarounded by running such a command
under --tool=none.
Jan Kratochvil suggested the better workaround finding out
spelling suggestions somehow were based on the processor time used by
the process. And so overriding clock to simply always return zero means
the process cannot observe the cpu time used.
The original RHEL test also converts an image to png. This version
of the test has the conversion to png disabled as it faills the test.
The failure is probably caused by some rounding issue which was
impossible to track down so far.
The test is currently only run on x86_64. There might be "Conditional jump
or move depends on uninitialised value(s)" warnings while running under valgrind,
but the test is to show the transformations work with and without valgrind.
gating.yaml only use tier0.functional, not scratch-build.validation.
The scratch-build.validation is for rebuilding the kernel, we don't
really need that as gating rule, since valgrind isn't part of the
kernel build chain.
plans/ci.fmf: Use tmt, not beakerlib, for how.
beakerlib is deprecated.
tests/quick-valgrind-sanity/main.fmf recommend only valgrind[-devel], gcc and make
This test doesn't use c++, fortran or 32bit glibc-devel.
