Search results
Page title matches
- ...ary that includes an initramfs with busybox, network config and strace for testing1 KB (176 words) - 12:21, 27 January 2020
- 426 bytes (68 words) - 11:58, 25 March 2019
- =QEMU 0.15 Release Testing= Add yourself to volunteer for QEMU 0.15 release testing.2 KB (297 words) - 16:56, 13 October 2011
- 2 KB (255 words) - 21:28, 16 April 2015
- ...rvice that perform continuous testing of the QEMU master branch as well as testing of each patch series that is submitted to the mailing list. Patchew also co1 KB (182 words) - 11:03, 1 August 2019
- | Debian testing || ? || <b><font color="green">rc2</font></b> || <b><font color="green">rc2 * Comprehensive libvirt testing [LuizCapitulino]7 KB (1,052 words) - 16:41, 29 November 2011
- 655 bytes (82 words) - 17:13, 9 July 2015
- | Debian testing || ? || ? || ? || ? || ? || ? * Comprehensive libvirt testing4 KB (549 words) - 13:08, 28 August 2012
- ...figure out which commit caused the breakage. This is primarily a tool for testing the toolchains but it could come up with QEMU regressions as well.1 KB (207 words) - 14:49, 14 July 2020
Page text matches
- ...m inputs to find bugs that lead to crashes or other program failures. Fuzz testing is a popular technique for finding security bugs.2 KB (340 words) - 07:01, 25 February 2022
- | Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]761 bytes (113 words) - 07:37, 4 November 2011
- ...e project is to build a driver framework in libqos to enable combinatorial testing. For more information, see [[Features/qtest_driver_framework]].760 bytes (114 words) - 15:35, 20 March 2018
- ===Testing=== * Alex Bennée (ARM testing, base enabling tree)4 KB (568 words) - 10:14, 4 August 2021
- ...ary that includes an initramfs with busybox, network config and strace for testing1 KB (176 words) - 12:21, 27 January 2020
- ...figure out which commit caused the breakage. This is primarily a tool for testing the toolchains but it could come up with QEMU regressions as well.1 KB (207 words) - 14:49, 14 July 2020
- == [[Testing/CI|Continuous Integration]] == * [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer cod9 KB (1,420 words) - 12:16, 12 July 2021
- Also see [[Planning/2.4/Testing]].882 bytes (126 words) - 16:12, 21 October 2015
- RISU (Random Instruction Sequence generator for Userspace testing) is a tool intended to assist in testing the implementation of models of3 KB (401 words) - 09:48, 4 February 2021
- ...ports a number of different public [[Testing/CI | CI systems]] to maximise testing coverage of code submitted to QEMU. By testing code via these CI systems prior to submission, contributors can reduce the7 KB (1,076 words) - 16:57, 12 May 2021
- * Get qemu-img compiling and start testing where it fails758 bytes (105 words) - 01:35, 19 July 2013
- Also see [[Planning/2.3/Testing]].931 bytes (133 words) - 11:24, 30 July 2015
- Also see [[Planning/2.0/Testing]].949 bytes (134 words) - 20:30, 6 August 2014
- existing QMPOutputVisitor, as well as debugging/testing migration via a well == (old) Testing ==8 KB (1,202 words) - 16:21, 24 April 2014
- == Testing ==4 KB (549 words) - 12:39, 22 March 2022
- ...erent targets (x86, mips, powerpc, ...). Images can be obtained from the [[Testing]] page. == Testing your changes ==7 KB (1,227 words) - 07:18, 18 November 2021
- === Testing and CI ===3 KB (277 words) - 09:09, 1 May 2024
- == Testing == ...data is prepared. We can use the space time to fill the cache queue. In my testing, the read speed can be improved from 0.9k/s to 500k/s6 KB (994 words) - 16:08, 17 October 2016
- Create a new guest (dpdk.img) for DPDK testing and then launch it: ===Testing vhost-user-net with DPDK testpmd===8 KB (1,079 words) - 17:00, 1 February 2023
- | [[Planning/1.2/Testing|Test Day]]. Community effort to shake out v1.2.0-rc bugs.1 KB (159 words) - 15:38, 11 October 2016