Lines Matching full:by

14 into the right shape, e.g. by replacing the 'stdout' python object to redirect
19 that there is no TAP-incompatible output written to stdio, e.g. either by
21 e.g. by capturing the stdout output of subprocesses (redirecting it to
42 You can run the functional tests simply by executing:
56 execute the file directly by specifying two environment variables first,
68 files around on disk by setting ```QEMU_TEST_KEEP_SCRATCH=1``` as an env
83   by the calls to the logging functions in the test code (e.g. by calling
114 By providing the "hash bang" line at the beginning of the script, marking
115 the file as executable and by calling into QemuSystemTest.main(), the test
118 functions in the right fassion (e.g. with TAP output that is required by the
129 QEMU command line, launching the QEMUMachine (by using ``self.vm.launch()``)
192 If it is not explicitly set by the test code, its default value will
201 by setting the ``QEMU_TEST_QMP_BACKDOOR`` env variable to refer
251 by the test.
257 by the test. By using the set_machine() function of the QemuSystemTest
270 unconstrained internet connection, so such tests should not be run by
287 This problem is solved by downloading the assets ahead of time, before
307 the assets without running the tests, you can do so by running::
311 The cache is populated in the ``~/.cache/qemu/download`` directory by
312 default, but the location can be changed by setting the
327 are recurring scenarios identified by the QEMU developers and the use of
345 skipped by default. The definition of *not safe* is also arbitrary but
354 Some tests are not working reliably and thus are disabled by default.
375 To avoid these timeout issues by default and to save some precious CPU
376 cycles during normal testing, such tests are disabled by default unless