<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/tools/testing/selftests/tc-testing/plugin-lib, branch v5.0</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.0</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.0'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2018-12-08T00:39:03Z</updated>
<entry>
<title>tc-testing: Implement the TdcResults module in tdc</title>
<updated>2018-12-08T00:39:03Z</updated>
<author>
<name>Lucas Bates</name>
<email>lucasb@mojatatu.com</email>
</author>
<published>2018-12-06T22:42:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=915c158deaf97be49e71250f43e1539542217962'/>
<id>urn:sha1:915c158deaf97be49e71250f43e1539542217962</id>
<content type='text'>
In tdc and the valgrind plugin, begin using the TdcResults module
to track executed test cases.

Signed-off-by: Lucas Bates &lt;lucasb@mojatatu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tc-testing: use a plugin to build eBPF program</title>
<updated>2018-10-05T21:44:56Z</updated>
<author>
<name>Davide Caratti</name>
<email>dcaratti@redhat.com</email>
</author>
<published>2018-10-04T16:34:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4c2d39bd40c1f34975bec070a8e43fa573a9c327'/>
<id>urn:sha1:4c2d39bd40c1f34975bec070a8e43fa573a9c327</id>
<content type='text'>
use a TDC plugin, instead of building eBPF programs in the 'setup' stage.
'-B' argument can be used to build eBPF programs in $EBPFDIR directory,
in the 'pre-suite' stage. Binaries are then cleaned in 'post-suite' stage.

Signed-off-by: Davide Caratti &lt;dcaratti@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: tc-testing: valgrindPlugin</title>
<updated>2018-02-15T20:38:33Z</updated>
<author>
<name>Brenda J. Butler</name>
<email>bjb@mojatatu.com</email>
</author>
<published>2018-02-14T19:09:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c25e4736867f73901de4fdb62c122ae2c6d91159'/>
<id>urn:sha1:c25e4736867f73901de4fdb62c122ae2c6d91159</id>
<content type='text'>
Run the command under test under valgrind.  Produce an extra set of
tap output for the memory check on each test.

Signed-off-by: Brenda J. Butler &lt;bjb@mojatatu.com&gt;
Acked-by: Lucas Bates &lt;lucasb@mojatatu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: tc-testing: nsPlugin</title>
<updated>2018-02-15T20:38:33Z</updated>
<author>
<name>Brenda J. Butler</name>
<email>bjb@mojatatu.com</email>
</author>
<published>2018-02-14T19:09:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a13fedbe56fef141aff7d584eba2a08daaf613cc'/>
<id>urn:sha1:a13fedbe56fef141aff7d584eba2a08daaf613cc</id>
<content type='text'>
Move the functionality of creating a namespace before the test suite
and destroying it afterwards to a plugin.

Signed-off-by: Brenda J. Butler &lt;bjb@mojatatu.com&gt;
Acked-by: Lucas Bates &lt;lucasb@mojatatu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: tc-testing: rootPlugin</title>
<updated>2018-02-15T20:38:33Z</updated>
<author>
<name>Brenda J. Butler</name>
<email>bjb@mojatatu.com</email>
</author>
<published>2018-02-14T19:09:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f6926e85eee9be08d05170af3a2266b8d7f9cdef'/>
<id>urn:sha1:f6926e85eee9be08d05170af3a2266b8d7f9cdef</id>
<content type='text'>
Move the functionality that checks for root permissions into a plugin.

Signed-off-by: Brenda J. Butler &lt;bjb@mojatatu.com&gt;
Acked-by: Lucas Bates &lt;lucasb@mojatatu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tools: tc-testing: Introduce plugin architecture</title>
<updated>2018-02-15T20:38:33Z</updated>
<author>
<name>Brenda J. Butler</name>
<email>bjb@mojatatu.com</email>
</author>
<published>2018-02-14T19:09:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=93707cbabcc8baf2b2b5f4a99c1f08ee83eb7abd'/>
<id>urn:sha1:93707cbabcc8baf2b2b5f4a99c1f08ee83eb7abd</id>
<content type='text'>
This should be a general test architecture, and yet allow specific
tests to be done.  Introduce a plugin architecture.

An individual test has 4 stages, setup/execute/verify/teardown.  Each
plugin gets a chance to run a function at each stage, plus one call
before all the tests are called ("pre" suite) and one after all the
tests are called ("post" suite).  In addition, just before each
command is executed, the plugin gets a chance to modify the command
using the "adjust_command" hook.  This makes the test suite quite
flexible.

Future patches will take some functionality out of the tdc.py script and
place it in plugins.

To use the plugins, place the implementation in the plugins directory
and run tdc.py.  It will notice the plugins and use them.

Signed-off-by: Brenda J. Butler &lt;bjb@mojatatu.com&gt;
Acked-by: Lucas Bates &lt;lucasb@mojatatu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
