Acceptance Tests: improve check-acceptance description

The "check-acceptance" make rule won't necessarily run *all* available
tests, because it employs a filter based on the currently configured
targets.  This change in the description of the rule makes that
behavior extra clear.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210924185506.2542588-3-crosa@redhat.com>

diff --git a/tests/Makefile.include b/tests/Makefile.include
index e69c4fae53e31d0c2963f5c2c52f64adb96b2c90..7426522bbed09665e17e89b703d7abbe06b65da9 100644 (file)
--- a/tests/Makefile.include
+++ b/tests/Makefile.include
@@ -16,7 +16,7 @@ ifneq ($(filter $(all-check-targets), check-softfloat),)
        @echo " $(MAKE) check-tcg            Run TCG tests"
        @echo " $(MAKE) check-softfloat      Run FPU emulation tests"
 endif
-       @echo " $(MAKE) check-acceptance     Run all acceptance (functional) tests"
+       @echo " $(MAKE) check-acceptance     Run acceptance (functional) tests for currently configured targets"
        @echo
        @echo " $(MAKE) check-report.tap     Generates an aggregated TAP test report"
        @echo " $(MAKE) check-venv           Creates a Python venv for tests"