1. 26 6月, 2019 1 次提交
  2. 02 4月, 2019 1 次提交
  3. 27 2月, 2019 1 次提交
  4. 14 2月, 2019 1 次提交
  5. 18 12月, 2018 1 次提交
  6. 20 11月, 2018 1 次提交
  7. 03 10月, 2018 1 次提交
  8. 04 9月, 2018 1 次提交
    • C
      Enables pylint w0621 · 628e35c3
      Caio Carrara 提交于
      This pylint checks for possible redefining outer names. Some occurrences
      was preserved with disable flag because they would broke some public
      api, like method/functions names or parameters.
      Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
      628e35c3
  9. 30 8月, 2018 1 次提交
  10. 28 8月, 2018 1 次提交
  11. 17 7月, 2018 1 次提交
  12. 13 6月, 2018 1 次提交
  13. 26 4月, 2018 1 次提交
  14. 28 3月, 2018 1 次提交
  15. 21 3月, 2018 1 次提交
  16. 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
  17. 01 3月, 2018 1 次提交
  18. 23 1月, 2018 1 次提交
  19. 19 12月, 2017 1 次提交
  20. 01 12月, 2017 1 次提交
  21. 23 11月, 2017 1 次提交
    • D
      resultsdb: Control note's size limit · ae373b15
      Dmitry Monakhov 提交于
      Currently test's note contains full job.state['fail_reason'].
      And it can be huge unreadable single line  backtrace which
      looks ugly in resultsdb_frontend. In my case it populate whole
      webpage. IMHO front end note should be small, if someone want to
      investigate failure reason we should goto logs link.
      
      This patch add config option which allow to limit note's size,
      which is limited by default to preserve original behaviour.
      
      Also map job.INTERRUPTED state to resultsdb.INFO because when human
      manually interrupts test he probably knows the reason, so test should
      not being treated as NEEDS_INSPECTION.
      Signed-off-by: NDmitry Monakhov <dmonakhov@openvz.org>
      ae373b15
  22. 22 11月, 2017 1 次提交
  23. 21 11月, 2017 1 次提交
  24. 17 10月, 2017 1 次提交
  25. 11 10月, 2017 1 次提交
  26. 21 9月, 2017 1 次提交
  27. 20 9月, 2017 1 次提交
  28. 16 8月, 2017 1 次提交
  29. 27 6月, 2017 1 次提交
  30. 13 6月, 2017 1 次提交
  31. 17 5月, 2017 1 次提交
  32. 25 4月, 2017 2 次提交
  33. 24 4月, 2017 1 次提交
  34. 21 4月, 2017 1 次提交