Search results
Page title matches
- ...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
- ...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
- 2 KB (271 words) - 17:13, 21 July 2021
- 1 KB (204 words) - 18:22, 15 February 2013
- 6 KB (839 words) - 15:12, 10 May 2024
- 2 KB (184 words) - 14:57, 14 February 2020
- '''DEPRECATED:''' we are in the process of deprecating Travis in favour of [[Testing/CI/GitLabCI|GitLab's CI system]] == Testing Changes to Travis ==1 KB (230 words) - 12:24, 15 February 2021
- 565 bytes (93 words) - 14:27, 3 April 2014
- '''DEPRECATED:''' We have now migrated all our cross-compile tests to the [[Testing/CI/GitLabCI|GitLab CI]] architecture. ...ble is used mostly to do our cross compile testing. It uses the existing [[Testing/DockerBuild|docker]] infrastructure to build out major architectures. The c1,003 bytes (142 words) - 11:34, 16 February 2021
- 625 bytes (91 words) - 14:50, 6 October 2020
- =QEMU 0.14 Release Testing= Add yourself to volunteer for QEMU 0.14 release testing.3 KB (435 words) - 05:13, 19 May 2011
- ...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
- ...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
- '''Summary:''' Improve the REST API to retrieve patch metadata, testing results, etc. from [http://patchew.org patchew.org] Patchew is an open source CI project to automate testing of patches submitted as emails on mailing lists. Currently Patchew has a s967 bytes (146 words) - 15:35, 20 March 2018
- ...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
- === Guest ABI automated testing === compatibility, we have no automated testing to detect common1 KB (218 words) - 18:51, 21 January 2019
- * QMP: [[ToDo/QMP|infrastructure]] and [[ToDo/QMPTesting|testing]]441 bytes (57 words) - 09:12, 10 January 2019
- ==Testing== Testing AES-128-CBC cipher:3 KB (450 words) - 19:41, 30 September 2023
- RISU (Random Instruction Sequence generator for Userspace testing) is a tool for testing CPU instructions with randomly generated opcodes. RISU generates random CPU2 KB (311 words) - 08:11, 11 March 2022
- ...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 (288 words) - 06:58, 25 February 2022
- ...tested against the program in order to find crashes and other bugs. Fuzz testing complements hand-written test suites by exploring the input space of a prog ...hardware registers randomly to make the device respond. QEMU has a device testing interface called "qtest" that accepts read/write and other commands over a3 KB (448 words) - 15:15, 17 May 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
- =QEMU 0.14 Release Testing= Add yourself to volunteer for QEMU 0.14 release testing.3 KB (435 words) - 05:13, 19 May 2011
- ...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