External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-21 19:02:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: get rid of 'make check' references

Browse Source 
Update the remaining 'make check' references after the
switch to meson/ninja.

The reference in testsuites.html.in was kept with a note that it is
the process for Libvirt 6.6.0 and older.

Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
This commit is contained in:
Daniel Henrique Barboza 2020-08-06 10:34:51 -03:00 committed by Erik Skultety
parent ae8a83c353
commit 53f62118c3
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/advanced-tests.rst
View File

@ -90,7 +90,7 @@ location where the file is stored.
$ VIR_TEST_FILE_ACCESS=1 VIR_TEST_FILE_ACCESS_OUTPUT="/tmp/file_access.txt" ./qemuxml2argvtest
#. The Valgrind test should produce similar output to
``make check``. If the output has traces within libvirt API's,
``ninja test``. If the output has traces within libvirt API's,
then investigation is required in order to determine the cause
of the issue. Output such as the following indicates some sort
of leak:

9
docs/api_extension.html.in
View File

@ -361,11 +361,10 @@
</p>
<p>
Once you have working functionality, run make check and make
syntax-check on each patch of the series before submitting
patches. It may also be worth writing tests for the libvirt-TCK
testsuite to exercise your new API, although those patches are
not kept in the libvirt repository.
Once you have working functionality, run ninja test on each patch
of the series before submitting patches. It may also be worth
writing tests for the libvirt-TCK testsuite to exercise your new API,
although those patches are not kept in the libvirt repository.
</p>
</body>
</html>

3
docs/testsuites.html.in
View File

@ -10,7 +10,8 @@
by developers before submitting patches upstream, it is also
suggested to have it run and pass as part of the packaging
process for distributions. It is run by launching:
<pre>make check</pre>
<pre>make check (libvirt 6.6.0 and older)</pre>
<pre>ninja test (libvirt 6.7.0 and newer)</pre>
in a source tree after compilation has finished. It doesn't
really make functional testing but checks that large portions
of the code not interacting directly with virtualization