- 02 1月, 2018 1 次提交
-
-
由 Balamuruhan S 提交于
test errors out if tcpdump is not installed in guest, handle it by checking and installing it. remove few autotest dependencies Signed-off-by: NBalamuruhan S <bala24@linux.vnet.ibm.com>
-
- 21 9月, 2015 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Clean up imports across the board in tp-qemu. The criteria followed was: 1) Remove unnecessary imports 2) Turn multi imports from a single entry point to one import per line. This increases both patch and source code readability. 3) Separate blocks of imports with a line: * Python standard library imports * Autotest imports * virttest imports * Internal tp-qemu imports 4) Remove try/except blocks refering autotest libs and stick with the virttest.staging copy This paves the way for the future removal of autotest references, replacing those references with avocado ones. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 18 9月, 2015 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
'virttest.aexpect' was refactored and turned to its own project. Let's update all the references to simply 'aexpect' Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 20 8月, 2014 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Add the appropriate context when we're checking the status of the background processes pre and post migration. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
If the cleanup command returns 1 on Linux, it means the migrate background process is already gone, and a failure already happened in that particular migration test. So, just ignore this specific failure at the cleanup stage. The problem is that under windows, the appropriate error code is 128 [1]. So we have to make the ignore error code configurable, and change the windows config file in virt-test (on a separate PR). [1] http://www.symantec.com/connect/forums/error-128-during-script-executionSigned-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 17 8月, 2014 1 次提交
-
-
由 Yiqiao Pu 提交于
This case will do following steps: - disable dma in guest kernel command line to make sure ide disk using pio - check the pio and dma status inside guest - run iozone in background - do tcp migration Signed-off-by: NYiqiao Pu <ypu@redhat.com>
-
- 20 3月, 2014 1 次提交
-
-
由 Feng Yang 提交于
This could help use record dst vm to env. Then we can record screendump for it. Signed-off-by: NFeng Yang <fyang@redhat.com>
-
- 07 3月, 2014 1 次提交
-
-
由 Feng Yang 提交于
Signed-off-by: NFeng Yang <fyang@redhat.com>
-
- 28 1月, 2014 1 次提交
-
-
由 Feng Yang 提交于
Signed-off-by: NFeng Yang <fyang@redhat.com>
-
- 19 12月, 2013 1 次提交
-
-
由 Cleber Rosa 提交于
There's no need to have the name of the "run_<name>" method (main test entry point) depend on the test name. So, for simplicity sake, let's just name the test entry point "run". I have decided to not fallback gracefully to the previous naming convention as I believe this can lead to confusion in the future. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 11 12月, 2013 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Sometimes, post migration run, we can run into a condition where tcpdump or the VM hangs at migration cleanup stage. After analyzing test logs, including VM logs, there's nothing that points out to any guest OS crash or similar condition. With that in mind, it is admissible to be more lenient when trying to kill the migration background command, and if a timeout happens when trying to kill it, be safe and try to shut down the vm gracefully. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
As the pre processing code already takes care of that anyway. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 10 9月, 2013 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Make virt-test to have a docstring style mostly compliant with the sphinx's [1] format, reStructured text. This means that we have to trade all '@' tags to be ':', mostly. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 09 9月, 2013 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
With the help of the PEP8 script, a semi-automated clean of the code base was made, and effectively changing some of the coding style rules of our code base: * No more 2 lines spacing among functions * No more combined module imports In the end, it was going to be too difficult to take into consideration E501 (line length > 80) errors and W601 (.has_key() is deprecated), so these were ignored, at least for now. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 06 6月, 2013 5 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Yiqiao Pu 提交于
Make the migration.py support migrate gzip in localhost Signed-off-by: NYiqiao Pu <ypu@redhat.com>
-
由 Yiqiao Pu 提交于
Get all the autotest support test as a guest stress running the guest. And Make the local migration also support ping-pong cycles. Add a stress test deamon to make sure the stress test will running in cycles while the guest ping-pong migration. change from v1: - Use BackgroundTest() to start the deamon thread instead of fork. Because of the child thread from fork() will get wrong status of the stress thread. - Modify this patch to suit for the newest tree change from v2: - Fix one IndentationError - Add more infomation about migration round Signed-off-by: NYiqiao Pu <ypu@redhat.com> Acked-by: NFeng Yang <fyang@redhat.com> Acked-by: NXiaoqing Wei <xwei@redhat.com> Fix issue local variable 'guest_stress_test' referenced before assignment. Also delete some while space in black line. Signed-off-by: NFeng Yang <fyang@redhat.com> Stop guest stress thread finally When some exception raised during migrate process, guest stress will run endless, This patch sets the stop bit in "finally" block and sets a timeout in "join()" function. Changes from v2: - Update stress_stop_cmd to "killall autotest". Changes from v1: - Kill background stress process in guest. Signed-off-by: NQingtang Zhou <qzhou@redhat.com>
-
由 Qingtang Zhou 提交于
changes from v1: - remove some debug info. Signed-off-by: NQingtang Zhou <qzhou@redhat.com> Signed-off-by: NYiqiao Pu <ypu@redhat.com> Acked-by: NFeng Yang <fyang@redhat.com> Acked-by: NAmos Kong <akong@redhat.com>
-
- 04 4月, 2013 1 次提交
-
-
由 Lukáš Doktor 提交于
This patch benefits from the better error message when key is missing in config params. Instead of custom handling of missing param it uses params[] directly. I modified those params, where I was 100% certain that they are required and doesn't have default value: * val = params.get(..) followed by if not val: raise... * int(params.get(...)) * params.get(...).split() * commands which require string (eg. session.cmd(params.get(...))) I didn't test all the tests before and after in order to verify possible typos but I used pylint before and after, watching for new errors (code rate before and after). Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 25 12月, 2012 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
A frequent request we've got from users is that the name 'kvm' makes assumptions that are not true for a lot of the use cases of the test suite. Then let's rename the subtest 'kvm' to 'qemu', making it more accurate. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 07 9月, 2012 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-