On Friday 03 November 2006 15:22, Jim Meyering wrote: > It is not onerous to require this, because it is so easy to automate. > In addition to running tests via "make check", each package can also > run its tests via e.g., > > env "PATH=/some/new/temp/dir:$PATH" make check 3> log > > where the temporary directory, /some/new/temp/dir, contains one or > more tiny wrapper scripts, each arranging to run a tested application > via valgrind. Here's one named "rm" that I've used in testing that > program for the GNU coreutils: > > #!/bin/sh > export PATH=/cu/src:/sbin:/usr/sbin:/bin > exec /usr/bin/valgrind -v --suppressions=/tmp/cu-vg --log-fd=3 \ > --leak-check=full --track-fds=yes --num-callers=15 -- rm "$@" Is there any way to make this easier? A wrapper around everything perhaps? Something that could be done in mock? -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpvfgLJl0OLO.pgp
Description: PGP signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
