diff options
| author | Alexander Köplinger <alex.koeplinger@outlook.com> | 2015-10-28 03:21:38 +0300 |
|---|---|---|
| committer | Alexander Köplinger <alex.koeplinger@outlook.com> | 2015-10-28 16:37:14 +0300 |
| commit | 2684e2fc3c9ced00f839f960573b022a42ad5586 (patch) | |
| tree | d148ccabfabb1f2e1c3054bfea3f18d6356a485e /acceptance-tests/Makefile.am | |
| parent | f0817577423cadc81984590d2283f9e93c9ad3de (diff) | |
[acceptance-tests] Write list of CoreCLR tests into file and pass it to test-runner
This shaved about 30 seconds off the time until the test-runner started on my machine compared to
passing the tests in the command line directly (we have *lots* of CoreCLR tests).
Diffstat (limited to 'acceptance-tests/Makefile.am')
| -rw-r--r-- | acceptance-tests/Makefile.am | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/acceptance-tests/Makefile.am b/acceptance-tests/Makefile.am index ead6212274d..235855d0638 100644 --- a/acceptance-tests/Makefile.am +++ b/acceptance-tests/Makefile.am @@ -69,7 +69,9 @@ coreclr-compile-tests: coreclr-validate $(MAKE) -j4 $(CORECLR_TESTSI_CS) $(CORECLR_TESTSI_IL) coreclr-runtest-managed: coreclr-validate test-runner.exe $(CORECLR_TESTSI_CS) $(CORECLR_TESTSI_IL) - @$(RUNTIME) ./test-runner.exe -j a --testsuite-name "coreclr" --expected-exit-code 100 $(CORECLR_TESTSI_CS) $(CORECLR_TESTSI_IL) + @echo $(CORECLR_TESTSI_CS) $(CORECLR_TESTSI_IL) | tr " " "\n" > coreclr-testlist.txt + $(RUNTIME) ./test-runner.exe -j a --testsuite-name "coreclr" --expected-exit-code 100 --input-file coreclr-testlist.txt + @rm -f coreclr-testlist.txt check-coreclr: coreclr-compile-tests coreclr-runtest-managed |