devel/testing/main.rst

9 tests you can run ``make check-help`` from either the source or build
13 the meson build system so can be run directly from the build tree,
51 Before running tests, it is best to build QEMU programs first. Some tests
83 3. Add the test to ``tests/unit/meson.build``. The unit tests are listed in a
150   the build in the meson.build file.
200 ``tests/qemu-iotests`` directory under the build directory, and run ``./check``
334   # ci - tests to run on build
368 build and test QEMU in predefined and widely accessible Linux
432   make docker-test-build@debian
435 is downloaded and initialized automatically), in which the ``test-build`` job
445 container build steps over and over again. This can be overridden
446 locally by using the ``NOCACHE`` build option:
460 executed before building the image under the build context directory. This is
462 for example, to make qemu-user powered cross build containers work.
476 party projects.  ``lcitool`` applies the mappings to a list of build
479 to generate build environments (dockerfiles and Cirrus CI variable files)
483 Adding new build pre-requisites
486 When preparing a patch series that adds a new build
489 available in the CI build environments.
496  * Run ``make lcitool-refresh`` to re-generate all relevant build environment
505  * Add an entry for the new build prerequisite to
512    Please note in the description that this is a new build pre-requisite
545    MAINTAINERS file for ``Build and test automation``.
573    Please note in the description that this is a new build pre-requisite
588 Different tests are added to cover various configurations to build and test
592 source and build it.
607    build QEMU and run tests from there, or press Ctrl-D to let the Docker
641 The test-tsan test will build using TSan and then run make check.
647 TSan warnings under docker are placed in files located at build/tsan/.
655 It is possible to build and test with TSan, with a few additional steps.
664 To build a tsan version of glib:
670    $ CFLAGS="-O2 -g -fsanitize=thread" meson build
671    $ ninja -C build
673 To configure the build for TSan:
685 …rt LD_LIBRARY_PATH=$glib_dir/build/gio:$glib_dir/build/glib:$glib_dir/build/gmodule:$glib_dir/buil…
687    $ ldd build/qemu-x86_64 | grep glib
703                       log_path=<build path>/tsan/tsan_warning
789 is run as part of the build. The final image will be tagged as
796 necessary packages to build QEMU. The basic usage is documented in ``Makefile``
803 command to run build test in an image. For example, ``make vm-build-freebsd``
804 will build the source tree in the FreeBSD image. The command can be executed
805 from either the source tree or the build dir; if the former, ``./configure`` is
847     $ ./netbsd --build-image --image /var/tmp/netbsd.img
854     # To build QEMU in guest
855     $ ./netbsd --debug --image /var/tmp/netbsd.img --build-qemu $QEMU_SRC
873 * Once the image is downloaded, users, SSH server and QEMU build deps should
885   - Necessary packages are installed to untar the source tarball and build
890   QEMU source tree, then configure/build it. Running "make check" is also
928 linux-user and softmmu TCG functionality. However to build test
943 compiler flags are needed to build for a given target.
945 If you have the ability to run containers as the user the build system
948 use the same container to build tests. However there are a number of
949 additional containers defined that have a minimal cross-build
960 You can build the tests for one architecture::
962   make build-tcg-tests-$TARGET
974 Tests can also be run directly from the test build directory. If you
975 run ``make help`` from the test build directory you will get a list of
1023 ``--enable-gcov`` option and build. Then run the tests as usual.