On Wed, Feb 15, 2017 at 03:26:31PM +0000, Ferruh Yigit wrote: > Since "make test" and "make test-build" does dependency resolving, they > check for all dependent components (lib and drivers) which takes a few > seconds. > > This is a good feature during development, but if the target is just > running unit test, that step is unnecessary, it is possible to compile > onece and run unit test multiple times, without checking any code update > > For this purpose, a new make rule "make test-run" added. Which just runs > the unit test, expects that unit test already compiled. > > Signed-off-by: Ferruh Yigit <ferruh.yi...@intel.com> > --- Sorry, I just don't see the point of having an extra command to maintain and document for the sake of a few seconds on a unit test run. How long does the run itself take compared to the time to check dependencies?
/Bruce
