1. 28 8月, 2018 1 次提交
  2. 27 8月, 2018 1 次提交
  3. 24 8月, 2018 1 次提交
  4. 22 8月, 2018 1 次提交
  5. 04 8月, 2018 3 次提交
  6. 25 7月, 2018 1 次提交
  7. 21 7月, 2018 1 次提交
  8. 17 7月, 2018 2 次提交
  9. 13 7月, 2018 1 次提交
  10. 12 7月, 2018 1 次提交
  11. 11 7月, 2018 1 次提交
  12. 10 7月, 2018 1 次提交
  13. 27 6月, 2018 1 次提交
    • C
      Test Loader: use enums from from Python 3.4 · 5e4c4d16
      Cleber Rosa 提交于
      This change reveleaed a couple of location in the symbolic names where
      not being used, but their special values were being evaluated.  Let's
      avoid using the special (and subtle) meaning of ALL (True) and
      DEFAULT/AVAILABLE (which evaluate to False).
      
      The enum library is part of the standard library, starting from 3.4
      (which is the mininum version we require for Avocado).  On Python 2.7,
      we can rely on the backport package.
      
      This is of course not necessary right now, but I feel that we can
      continue modernizing the code base, and not wait for 2020 and then be
      liberated to use newer constructs and libraries.
      
      Reference: https://trello.com/c/k90E1kdg/1357-loader-remove-compatibility-aliasesSigned-off-by: NCleber Rosa <crosa@redhat.com>
      5e4c4d16
  14. 26 6月, 2018 1 次提交
  15. 21 6月, 2018 1 次提交
  16. 13 6月, 2018 1 次提交
  17. 11 6月, 2018 1 次提交
    • L
      optional_plugins: Limit fabric version to <2.0.0 · 62433b53
      Lukáš Doktor 提交于
      The fabric-2.0.0 is a complete rework of fabric using different
      approach and will require many changes to our code. Let's keep using the
      1.x.y version for now.
      
      The fabric3 is still only based on 1.x.y branch but let's also limit
      that one as it is based on the original fabric so it's expected that
      they might eventually come-up with 2.x.y py3 fork.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      62433b53
  18. 10 5月, 2018 1 次提交
  19. 26 4月, 2018 1 次提交
  20. 19 4月, 2018 2 次提交
  21. 14 4月, 2018 1 次提交
  22. 28 3月, 2018 1 次提交
  23. 27 3月, 2018 1 次提交
    • C
      HTML plugin: check for the presence of the params key · 37ba6d0a
      Cleber Rosa 提交于
      And not only for the content of params, assuming the existence of
      params.  This fixes the following error:
      
         $ avocado run passtest.py --vm-domain f26 --vm-username root
         JOB ID     : 488c8f26de7b52707e8ddb2b89d0f03a0622391d
         JOB LOG    : /home/cleber/avocado/job-results/job-2018-03-26T16.58-488c8f2/job.log
         DOMAIN     : f26
         LOGIN      : root@f26 (TIMEOUT: 120 seconds)
          (1/1) passtest.py:PassTest.test: PASS (0.01 s)
         RESULTS    : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
         JOB TIME   : 1.39 s
         Error running method "render" of plugin "html": 'params'
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      37ba6d0a
  24. 24 3月, 2018 1 次提交
    • C
      Lint: W0622 fixes · 7fb38a04
      Cleber Rosa 提交于
      The following two issues come up on the CI environment:
      
          ************* Module avocado_runner_remote
          W0622: 51,0: ConnectionError: Redefining built-in 'ConnectionError'
          ************* Module tests.test_mux
          W0622:130,8: TestMuxTree.test_basic_functions: Redefining built-in 'ascii'
      
      And are fixed here.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      7fb38a04
  25. 22 3月, 2018 3 次提交
  26. 21 3月, 2018 1 次提交
  27. 18 3月, 2018 1 次提交
    • A
      test results: optimize params information · d5076fac
      Amador Pahim 提交于
      Currently we propagate to test results the AvacadoParams object used by
      the test. Holding that object in the test results makes the Avocado
      process to consume a lot of memory.
      
      For instance, in an Avocado job with 5000 tests (passtest.py), with
      Avocado-VT in place, the Job object grows up from 59MB before running
      the tests to 274MB after running the tests, a 215MB growth::
      
          (Pdb) pre_tests
          Partition of a set of 440754 objects. Total size = 59066528 bytes.
      
          (Pdb) post_tests
          Partition of a set of 1570821 objects. Total size = 274340184 bytes.
      
          (Pdb) growth
          Partition of a set of 1130073 objects. Total size = 215274464 bytes.
      
      Since the 'params' item is important for both the HTML report and the
      ResultsDB report, instead of dropping the 'params' item from the
      results, this patch parses the AvocadoParams, populating the test
      results with a list of tuples, each one containing the 'path', 'key' and
      'value' per parameter basis. This improves the situation a lot. The same
      Avocado Job will now only grow up from 59MB to 89MB::
      
          (Pdb) pre_tests
          Partition of a set of 440747 objects. Total size = 59066424 bytes.
      
          (Pdb) post_tests
          Partition of a set of 840812 objects. Total size = 89619904 bytes.
      
          (Pdb) growth
          Partition of a set of 400071 objects. Total size = 30554288 bytes.
      
      The HTML and ResultsDB plugins were adapted accordingly.
      Signed-off-by: NAmador Pahim <apahim@redhat.com>
      d5076fac
  28. 13 3月, 2018 1 次提交
    • C
      test_fingerprint_order: work around dict items representation · 27656da5
      Cleber Rosa 提交于
      In Python 3, the order of a dictionary items will be different than
      under Python 2.  To not have to change the supporting code to return
      OrderedDicts, let's just simplify the comparison, breaking them down
      into each dictionary item.
      
      This fixes the varianter_yaml_to_mux plugin unittest failure under
      Python 3:
      
          ======================================================================
          FAIL: test_fingerprint_order (tests.test_mux.TestMuxTree)
          ----------------------------------------------------------------------
          Traceback (most recent call last):
            File "/home/cleber/src/avocado/avocado/optional_plugins/varianter_yaml_to_mux/tests/test_mux.py", line 231, in test_fingerprint_order
              self.assertEqual(str(variant1), "{'paths': '', 'variant': "
          AssertionError: "{'variant_id': 'child1-child2-9154', 'varia[65 chars] ''}" != "{'paths': '', 'variant': [TreeNode(name='ch[65 chars]54'}"
          - {'variant_id': 'child1-child2-9154', 'variant': [TreeNode(name='child1'), TreeNode(name='child2')], 'paths': ''}
          + {'paths': '', 'variant': [TreeNode(name='child1'), TreeNode(name='child2')], 'variant_id': 'child1-child2-9154'}
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      27656da5
  29. 08 3月, 2018 4 次提交
  30. 01 3月, 2018 1 次提交
  31. 27 2月, 2018 1 次提交