1. 27 2月, 2019 1 次提交
  2. 20 2月, 2019 3 次提交
  3. 14 2月, 2019 2 次提交
  4. 12 2月, 2019 2 次提交
    • L
      Add support for SettingsPlugin · b4b3116b
      Lukáš Doktor 提交于
      With this implementations plugins will be able to modify the path list
      for "avocado.core.settings". Mainly it should be used to register extra
      configuration, but users should also be able to reorder/remove/modify
      the path to default config files.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      b4b3116b
    • L
      settings: Change the way config files are processed · ae437e42
      Lukáš Doktor 提交于
      Originally we only processed files that existed and when they were read
      we updated list of config locations and in case of no return list of
      failed-to-read paths. Anyway the "config.read" function accepts list of
      config files and returns list of successfully parsed files. Missing
      files are automatically skipped and broken files raise exception, so
      let's just simply create list of to-be-read files and feed it into the
      "config.read" function.
      
      As a result the list of not-read files actually works, still in this
      version it's only displayed on "avocado config", where users can get
      notion of all possible locations and in "avocado run" only parsed files
      are displayed as it doesn't seem important enough to log them there to
      me.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      ae437e42
  5. 07 2月, 2019 2 次提交
  6. 24 1月, 2019 1 次提交
  7. 12 1月, 2019 1 次提交
  8. 18 12月, 2018 1 次提交
  9. 13 12月, 2018 1 次提交
    • C
      Tags: add support for tag key/val match · 022dcea4
      Cleber Rosa 提交于
      Up to this point, the matching and thus filtering of tags was flat.
      Now, the individual value of the required keys are checked.
      
      For instance, if you have a test such as:
      
          class My(Test):
              def test(self):
                  """
                  🥑 tags=classification:tier1
                  """
                  ...
      
      Both of these filter conditions will match:
      
       $ avocado run -t classification test.py
       $ avocado run -t classification:tier1 test.py
      
      But this won't match:
      
       $ avocado run -t classification:tier2 test.py
      
      Also, similarly to the how there's support for including tests that
      have no tags at all, there's support for including tests that are
      not tagged with a specific keys.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      022dcea4
  10. 20 11月, 2018 1 次提交
  11. 03 10月, 2018 1 次提交
  12. 02 10月, 2018 1 次提交
    • C
      Add core test parameter passing support (non-varianter based) · 252f8be2
      Cleber Rosa 提交于
      Currently, the only way to pass parameters to Avocado is by using the
      variants layer, that is, one of the existing varianter plugin
      implementations.  This was based on earlier design decisions, that
      we're trying to fix without breaking expectation and compatibility.
      
      While it'd makes sense to support parameters created by the varianter
      layer itself, together with non-varianter parameters, it seems that we
      can start by adding support for one or the other being used at a time.
      
      This commit does exactly that: add support for a method of passing
      parameters via the command line for all tests in a job, without
      having to resort to the varianter.  When the varianter is used,
      it takes precedence and the core test parameter passing support
      is ignored.
      
      This should solve a number of use cases that require one-time
      executions of tests with different parameters, especially
      executions during test development and debugging.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      252f8be2
  13. 28 8月, 2018 1 次提交
  14. 31 7月, 2018 1 次提交
  15. 25 7月, 2018 1 次提交
  16. 17 7月, 2018 1 次提交
  17. 11 7月, 2018 1 次提交
  18. 10 7月, 2018 2 次提交
  19. 23 6月, 2018 1 次提交
  20. 13 6月, 2018 1 次提交
  21. 11 6月, 2018 2 次提交
  22. 09 6月, 2018 1 次提交
    • L
      utils.process: Ignore decode-errors when logging the output · 4540e937
      Lukáš Doktor 提交于
      It might happen that user runs process with encoding that is ritcher
      than system one. This is fine by the process as internally it stores
      encoded bytes object, but the drainer might fail attempting to log the
      output.
      
      Those failures should not be critical as, under described circumstances,
      the unavailability of the output is expected and should not prevent the
      execution. Let's simply replace those characters using 'replace' (the
      'xmlcharrefreplace' might fail with ASCII coder) and keep processing the
      data.
      
      To simplify error handling new "astring.to_text" argument "errors" is
      added.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      4540e937
  23. 06 6月, 2018 1 次提交
  24. 18 5月, 2018 1 次提交
  25. 26 4月, 2018 1 次提交
  26. 16 4月, 2018 1 次提交
  27. 28 3月, 2018 1 次提交
  28. 22 3月, 2018 2 次提交
  29. 14 3月, 2018 1 次提交
  30. 08 3月, 2018 1 次提交
  31. 01 3月, 2018 1 次提交
  32. 27 2月, 2018 1 次提交