WSL2-Linux-Kernel/tools/testing/ktest/examples
Steven Rostedt (Red Hat) 4283b169ab ktest: Add make_warnings_file and process full warnings
Although the patchcheck test checks for warnings in the files that were
changed, this check does not catch warnings that were caused by header
file changes and the warnings appear in C files not touched by the
commit.

Add a new option called WARNINGS_FILE. If this option is set, then the
file it points to is read before bulid, and the file should contain a
list of known warnings. If a warning appears in the build, this file is
checked, and if the warning does not exist in this file, then it fails
the build showing the new warning.

If the WARNINGS_FILE points to a file that does not exist, this will
cause any warning in the build to fail.

A new test is also added called "make_warnings_file". This test will
create do a build and record any warnings it finds into the
WARNINGS_FILE. This test is something that can be run before other tests
to build a warnings file of "known warnings", ie, warnings that were
there before your changes.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2013-01-31 10:24:56 -05:00
..
include ktest: Add make_warnings_file and process full warnings 2013-01-31 10:24:56 -05:00
README ktest: Add README to explain what is in the examples directory 2012-05-22 00:15:12 -04:00
crosstests.conf ktest: Add an example config that does cross compiling of several archs 2012-05-22 00:11:00 -04:00
kvm.conf ktest: Add kvm.conf example config 2012-05-22 00:10:12 -04:00
snowball.conf ktest: Add the snowball.conf example config 2012-05-22 00:13:32 -04:00
test.conf ktest: Add useful example configs 2012-05-22 00:08:30 -04:00

README

This directory contains example configs to use ktest for various tasks.
The configs still need to be customized for your environment, but it
is broken up by task which makes it easier to understand how to set up
ktest.

The configs are based off of real working configs but have been modified
and commented to show more generic use cases that are more helpful for
developers.

crosstests.conf - this config shows an example of testing a git repo against
    lots of different architectures. It only does build tests, but makes
    it easy to compile test different archs. You can download the arch
    cross compilers from:
  http://kernel.org/pub/tools/crosstool/files/bin/x86_64/

test.conf - A generic example of a config. This is based on an actual config
     used to perform real testing.

kvm.conf - A example of a config that is used to test a virtual guest running
     on a host.

snowball.conf - An example config that was used to demo ktest.pl against
     a snowball ARM board.

include/  -  The include directory holds default configs that can be
    included into other configs. This is a real use example that shows how
    to reuse configs for various machines or set ups. The files here
    are included by other config files, where the other config files define
    options and variables that will make the included config work for the
    given environment.