1. 08 8月, 2018 1 次提交
  2. 13 4月, 2018 1 次提交
  3. 11 4月, 2018 1 次提交
  4. 04 4月, 2018 1 次提交
  5. 27 3月, 2018 1 次提交
  6. 05 12月, 2017 1 次提交
  7. 08 11月, 2017 1 次提交
  8. 23 10月, 2017 1 次提交
  9. 21 9月, 2017 1 次提交
  10. 18 8月, 2017 1 次提交
  11. 29 6月, 2017 2 次提交
  12. 14 6月, 2017 1 次提交
  13. 11 4月, 2016 1 次提交
  14. 07 4月, 2016 1 次提交
  15. 31 3月, 2016 1 次提交
  16. 18 3月, 2016 1 次提交
  17. 21 9月, 2015 1 次提交
    • L
      tp-qemu: Import cleanups · 288ce897
      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>
      288ce897
  18. 17 2月, 2015 1 次提交
  19. 20 8月, 2014 1 次提交
  20. 08 5月, 2014 1 次提交
  21. 01 5月, 2014 1 次提交
  22. 16 4月, 2014 1 次提交
  23. 26 3月, 2014 4 次提交
  24. 16 3月, 2014 5 次提交
  25. 04 2月, 2014 2 次提交
  26. 31 1月, 2014 1 次提交
  27. 21 1月, 2014 2 次提交
  28. 19 12月, 2013 1 次提交
    • C
      virt: change test entry point method name · 6124219f
      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>
      6124219f
  29. 21 11月, 2013 1 次提交
    • L
      virttest.utils_env: Solve the env["address_cache"] RuntimeError issue · 351091c1
      Lucas Meneghel Rodrigues 提交于
      There is a background tcpdump thread that records DHCP leases
      in the env["address_cache"] dictionary. Sometimes, this thread
      might write to this dictionary while the environment object is
      being saved, triggering a RuntimeError in virt-test.
      
      So the solution involves:
      
      1) Creating a save lock, (a threading reentrant lock object),
      that is acquired by the env.save() method when it wants to
      save env.data to a pickle file, and for methods that alter
      env.data.
      
      2) Move the tcpdump thread to a env object attribute, rather
      than one of the keys of env.data, given that the lock object
      can't be pickled.
      
      With the implementation of env.save_lock, we can also fix
      the problem identified by the locking unittest. The base of
      the solution was Pavel's idea, including a good deal of the
      implementation, so kudos to him.
      Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
      351091c1
  30. 18 11月, 2013 1 次提交