On Wed, Feb 15, 2017 at 05:41:08PM +0000, Ferruh Yigit wrote: > On 2/15/2017 5:07 PM, Bruce Richardson wrote: > > 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? > > It is matter of choice, it does not take much time for "make test", but > still I thought it is handy to have a rule only to run the test. > > I don't expect much maintenance cost with this, also I don't have strong > opinion to keep it. > Yes, I suppose it isn't much maintenance cost indeed, so if nobody else cares, I'm ok with it too.