Lines Matching refs:be

22    features. As new tests will be added, config options list will be updated.
24 *  All tc-related features being tested must be built in or available as
31    because the kernel did not support a specific feature. (This will be
39 The path to the tc executable that will be most commonly tested can be defined
52 commands being tested must be run as root.  The code that enforces
58 network namespace and creates a veth pair which may be used in those test
60 to tdc when starting a test run; the veth pair will still be created
69 output captured from the failing test will be printed immediately following
76 One run of tests is considered a "test suite" (this will be refined in the
89 can be run next.  These two stages require any commands run to return
103 The tdc_config.py file contains multiple values that can be altered to suit
104 your needs. Any value in the NAMES dictionary can be altered without affecting
105 the tests to be run. These values are used in the tc commands that will be
106 executed as part of the test. More will be added as test cases require.
133                         a physical device will be skipped)
192 must be called "SubPlugin" so tdc can find them.  They are
210 full command to be executed.  This allows for last-minute adjustment
226 plugins.  It will be detected at run time and invoked at the
234       while also setting up dummy devices to be used in testing.