Skip to content

A
avocado

openeuler / avocado

通知 0
Star 0
Fork 0
A
avocado

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 08 3月, 2019 1 次提交
  3. 06 12月, 2018 1 次提交
  5. 17 11月, 2018 1 次提交
  7. 29 8月, 2018 1 次提交
    • 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
  9. 23 8月, 2018 1 次提交
  11. 18 7月, 2018 3 次提交
  13. 23 2月, 2018 1 次提交
    • C
      Python 3: do not allow failures on CI, but only run unittests and doc · 494405ae
      由 Cleber Rosa 提交于 
      This removes the exception of allowing failures on the Travis CI jobs
with Python 3, while, at the same time, temporary restricts Python 3
jobs to run only unittests and the documentation build for the Avocado
core.  That is, it excludes the functional tests, and the optional
plugin's tests.

While it may look like a step back, it's actually a step forward in the
Python 3 port, because now any regression on the unittests will be caught.
And, when the additional fixes are applied to address the functional tests
and plugin's tests, the whole set of tests will be enabled for Python 3.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      494405ae
  15. 17 2月, 2018 1 次提交
  17. 19 1月, 2018 1 次提交
  19. 18 12月, 2017 3 次提交
  21. 20 11月, 2017 1 次提交
    • A
      Travis fixes · d4758342
      由 Amador Pahim 提交于 
      - Revert "travis: Use parallel check in travis"

    This reverts commit 4b296996.

    Parallel check was enabled in Travis, but it's overloading the system
    and making the time sensitive tests to FAIL.

- avocado.utils.process: fix default prefix

    Log prefix needs at least the %-style string formatter. Let's include
    that as the default so we don't break under 'no prefix'.
Signed-off-by: NAmador Pahim <apahim@redhat.com>
      d4758342
  23. 15 11月, 2017 2 次提交
  25. 21 8月, 2017 1 次提交
    • A
      Fix Travis check · 6574c1dc
      由 Amador Pahim 提交于 
      With the EOL of Ubuntu 12.04, Travis CI is now running our tests using
Ubuntu 14.04. With this change, our check started to fail.

Even though I'm not sure about the reasons, I could make it work by
using a newer version of Pillow and also installing libvirt-python from
pip, since it's not working in the virtualenv if installed from apt.
Signed-off-by: NAmador Pahim <apahim@redhat.com>
      6574c1dc
  27. 27 6月, 2017 1 次提交
  29. 26 6月, 2017 1 次提交
  31. 15 5月, 2017 2 次提交
  33. 06 2月, 2017 2 次提交
    • C
      Python 2.6: drop support and require Python 2.7 or greater · 9401c928
      由 Cleber Rosa 提交于 
      The main reason for supporting Python 2.6 was the EL6 distros.
Although they are still important, our users are running a combination
of Avocado LTS and Avocado-VT.  That allows us to drop support for
Python 2.6 on master (and further Avocado releases).

Also, with Python 2.6 being dropped as a supported platform, the
version of the stevedore library can be simplified.  Let's reflect
that on both setup.py and requirements*.txt.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      9401c928
    • C
      Travis-CI: install dependencies which are too fragile with PIP · 0b6560de
      由 Cleber Rosa 提交于 
      The libvirt Python bindings are very very hard to install from source.
On Travis, let's rely on pre-built versions from official distro
packages.

This has not been an issue so far because of the conditional treatment
given on `avocado/core/virt.py`.  When the import fails,
`VIRT_CAPABLE` was set to `False`.

The goal of this change is twofold:

1) Enable the dependency on Travis so that the tests from
`selftests/unit/test_vm.py` are run.

2) Prepare for the split of the runner packages, in which there will
be no conditionals of the libvirt import, since the installation of
the package should mean that the dependencies are also fulfilled.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      0b6560de
  35. 03 2月, 2017 1 次提交
    • L
      selftests: Add check for not-producing-results by running selftests · 7f79b782
      由 Lukáš Doktor 提交于 
      It happened couple of times that running our selftests produced a new
entries in the default results directory. Let's use this optional check
to avoid such issue.

To enable this check one has to set "AVOCADO_RESULTSDIR_CHECK" env
variable. This check is enabled in travis as I do not expect travis to
run avocado tests while running the selfcheck, unlike on developer
computers.

Note the check is rather simple and only assumes the default results
directory. For selfcheck I think it's enough.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      7f79b782
  37. 10 1月, 2017 1 次提交
    • L
      travis: Use the same check for all commits · f1ca8dc9
      由 Lukáš Doktor 提交于 
      Currently we check the first commit differently, then all the other
commits. It was better as individual failures were distinguished by
colors. We added the support for colors to our "checkall" script making
the "make check" similarly synoptic so there is no need to treat the
first commit differently anymore.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      f1ca8dc9
  39. 26 9月, 2016 1 次提交
  41. 14 9月, 2016 1 次提交
  43. 03 5月, 2016 3 次提交
  45. 26 4月, 2016 1 次提交
    • C
      Travis: improve cleanup of per-commit environment · a21f1bc7
      由 Cleber Rosa 提交于 
      When running the per-commit checks on CI, the previous environment is
not as clean as it should be.

One example is when a given work introduces a new plugin. First the
HEAD of the branch is tested, which includes the installation of the
new plugin.  Then, the per-commit checks would return to the first
commit in the branch, which doesn't contain the plugin, but the
environment still knows about it.  This is a matter of forcing the
clean up of setuptools entrypoints (or any setuptools generated info
for that matter).

While adding the deeper cleaning, it seemed useful to split the
Makefile "link" target into "develop", which runs "python setup.py
develop" on the Avocado source tree alone.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      a21f1bc7
  47. 01 3月, 2016 1 次提交
  49. 18 2月, 2016 1 次提交
    • H
      Use environment marker for conditional requirements · 03c04b98
      由 Hao Liu 提交于 
      Managing different requirements files for different python version
requires much more efforts when the requirements became too complex.

This issue emerged when a required package `stevedore` decide not
supporting Python 2.6 since version `1.11.0`.

```
>>> import stevedore
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/site-packages/stevedore/__init__.py", line 23, in <module>
    LOG.addHandler(logging.NullHandler())
AttributeError: 'module' object has no attribute 'NullHandler
```

Pip provides a feature named [Environment
Markers](https://www.python.org/dev/peps/pep-0496/) for requirements
file to include specific packages conditionally which could properly
solve this issue.

This fix:
1. Use environment markers and merge python version specific
requirements files;
2. Remove python version specific requirements files references in
`Makefile` and Travis configuration;
3. Use `pip install -r requirements.txt` to replace per-line package
installation;
4. Restrain package `stevedore` on Python 2.6 to `1.10.0`.
Signed-off-by: NHao Liu <hliu@redhat.com>
      03c04b98
  51. 11 2月, 2016 1 次提交
  53. 09 2月, 2016 1 次提交
  55. 18 12月, 2015 1 次提交
    • C
      Travis CI: enable setuptools entry points · 5b643bd1
      由 Cleber Rosa 提交于 
      The new plugin architecture depends on setuptools entry points being
properly registered. These entry points are defined in a `setup.py`
file, as the `entrypoints` parameter, but they are only effective when
they become an `entry_points.txt` file inside a
`<your_project>.egg_info` directory.

This can happen in two ways:

1) installing the package, that is, running `$ python setup.py
install`

2) enabling the development mode, that is, running `$ python setup.py
develop`.

The approach chosen here is the latter, because it's faster, doesn't
require a full install and points to the checked out source code tree.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      5b643bd1
  57. 06 10月, 2015 1 次提交
  59. 30 9月, 2015 1 次提交
  61. 03 9月, 2015 1 次提交
    • C
      Selftests: drop nose usage for plain unittest discovery · e9c0d813
      由 Cleber Rosa 提交于 
      The unittest module, and unittest2 backport on Python 2.6, is capable of
finding unittests and running them. So, effectively, we do not need nose
at all.

This patch removes the dependency on nose, replacing the run script
with a version based solely on the unittest module.

One change of functionality is that run now looks and runs tests in the
standard selftests directories (unit, functional, doc), and does not
accept command line arguments. If one wants to run a subset of them,
it's pretty easy to just use the unittest module for that:

 $ python -m unittest discover -s selftests/unit
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      e9c0d813