1. 18 9月, 2018 8 次提交
  2. 17 9月, 2018 1 次提交
  3. 15 9月, 2018 1 次提交
    • C
      External Runner: support relative paths given on the command line · 89704618
      Cleber Rosa 提交于
      I was trying to use the external runner, in a reasonably simple way:
      from within a project (QEMU) build dir, I'd run:
      
       $ avocado run --external-runner=tests/qemu-iotests/check \
         --external-runner-chdir=runner -- 001 002
      
      But, what should work, did not.  The problem is with the non-absolute
      path to the external runner, that is needed because we're changing
      directories.
      
      Absolute paths won't hurt otherwise (when no chdir is done), so it's
      always done here.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      89704618
  4. 12 9月, 2018 1 次提交
  5. 07 9月, 2018 16 次提交
  6. 06 9月, 2018 2 次提交
  7. 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
  8. 01 9月, 2018 3 次提交
  9. 31 8月, 2018 1 次提交
  10. 30 8月, 2018 1 次提交
  11. 29 8月, 2018 5 次提交
    • C
      4f3fbcda
    • C
      203770f1
    • C
      Improve dependency specification for tests and ci · 1cd91fd6
      Caio Carrara 提交于
      The dependencies for selftests and CI execution was split in two
      requirements files. It causes issues with libs being in different
      versions when tests are executed locally and in CI environment. To
      reduce theses issues and others the changes bellow was done.
      
      All dependencies listed in requirements.txt are now specified only in
      setup.py properly. This way we avoid duplications or missing
      requirements that are necessary for avocado.
      
      It also could be done keeping only requirements.txt file and loading it
      in setup.py module. However, since avocado-framework have not clear use
      case of requirements being installed via `pip install requirements.txt`,
      it's better keep the dependencies only in setup module.
      
      It was removed the requirements file only for CI purpose and
      updates the requirements for selftest. This way we can have proper
      dependencies installed when run selftests both in local or CI
      environements.
      
      The requirements-selftest was updated: Setuptools was removed since it's
      already a dependency from avocado itself. Pep8 was removes since it's
      already a dependecy from inspektor. Since we run lint checks by
      inspektor it's better let it manage de pep8 (or pycodestyle) dependency
      Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
      1cd91fd6
    • C
    • C
      avocado.utils.vmimage: differentiate against base and concrete classes · e98d3c1b
      Cleber Rosa 提交于
      First of all, a disclaimer: this is hackish.  But, it's the simplest
      and thus best fix I could think of.
      
      What happens here is that this module makes no distintcion between
      what is a base class "abstract" class, and a concrete class.  With the
      goal of reducing code duplication, a goal that will remain valid here
      and in other modules, it made sense to create a common Fedora class.
      
      Now, because only being a ImageProviderBase suffices, the
      FedoraImageProviderBase class, which is not intended to be used as a
      concrete (final) class, is being carried along and its "name" is
      checked, causing crashes.
      
      This introduces the ad-hoc, hackish, notion, that a concrete
      ImageProvider is one that contains a name.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      e98d3c1b