- 18 12月, 2015 3 次提交
-
-
由 Cleber Rosa 提交于
At this point, no plugin support exists in Avocado. This is in preparation for the new plugin code to be cleanly introduced. The plugins that play a role in the plugin architecture have been removed, since they wouldn't be functional under the new plugin management code. The ones that are add extra functionality to Avocado have been kept, and will be ported to the new architecture. Also, most of the functional tests have been temporarily disabled. The reason is that most of them run avocado, which depends on the run command, which in turn, depends on the plugin archicture code. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 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>
-
由 Cleber Rosa 提交于
This shows a more succint version of the help message (the so called "usage" information). It's a certainly a matter of taste and change of behavior, so this is marked as an RFC. It also avoids a hackish injection of the print_help method as the default dispatch method. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 16 12月, 2015 9 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Makefile: Add requirements-python26 [v2]
-
由 Cleber Rosa 提交于
Again, let's short target names. It helps with typing and makes the documentation fit better most screens. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The install requirements targets are really best effort. PIP can fail in so many ways. So, let's not attempt to detect if the target ran successfully or not. This is important because it may prevent other chained command lines and targets to attempted an execution. Also attempt to install Python 2.6 requirements early, since they are simpler than the other requirements and pretty much basic back ported libraries. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Let's separate those to aid in a quick visual identification. Also, users are probably different among those three target groups. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
IMHO short names for Makefile targets are desirable, so let's shorten the names of the Debian related targets. Also, they better match the RPM target names like that. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Simple attempt to give the help message output a better look. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lukáš Doktor 提交于
To simplify usage with python2.6 add requirements-python26.txt which adds python2.6 requirements (on top of requirements.txt). It includes booth avocado and selftest dependencies and is automatically invoked when running on system with python 2.6. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
Without the --upgrade the installation fails when the package of incompatible version is already installed. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Cleber Rosa 提交于
This fixes the recently introduced commit 5f7bafd0, running the skip function instead of passing the function itself to `unittest.skipIf`. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 15 12月, 2015 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
selftests/functional/test_output.py: skip test on absence of PIL library
-
由 Cleber Rosa 提交于
The `test_gendata` test of `OutputTest` runs the example test `gendata.py`, but the `gendata.py` itself has a conditional in one of the tests that make use of the PIL (aka Pillow package) library and does nothing if it's missing. PIL (Pillow) is highly dependent on C compilers and libraries to be able to build itself. This makes systems it harder to run the full Avocado self tests on more diverse (usually minimalist) systems. So, let's make that functional test optional, if the libraries are not present. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 12 12月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
Human output: functional test fixes [v2]
-
- 11 12月, 2015 1 次提交
-
-
由 Cleber Rosa 提交于
There are a couple of functional unittests that assume that a given output was produced by the regular UI, that is, the Human output format. That is fine, since they're functional tests. But, some situations lead to test errors, instead of pointing failures. Let's turn those into explicit checks and fail properly instead of producing errors. Note: These errors were visible when the human output was disabled, in the plugin overhaul work, but the fixes still make sense independently of that work. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 10 12月, 2015 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
scripts.avocado: Use /var/tmp if TMP not set in env
-
由 Lukáš Doktor 提交于
Some distributions mount /tmp as tmpfs, which does not implement all usual filesystem functions, like O_DIRECT flag. This causes problems for some tests. Let's check if the user already set TMP in environment and if not, try to use /var/tmp by default. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 08 12月, 2015 1 次提交
-
-
由 Cleber Rosa 提交于
-
- 07 12月, 2015 3 次提交
-
-
由 Cleber Rosa 提交于
-
由 Lukáš Doktor 提交于
virtualenv: allow tests to run properly on them
-
由 Cleber Rosa 提交于
While going through the dependency list (requirements*.txt files) and performing our self tests out of virtual environments, I noticed that some tests are run outside the virtual environments. The reason is that, even though the virtual environment is activated for the test session (and say, `which python` gives `/venv/bin/python`), we have hard coded `/usr/bin/python` in most places. According to the some discussions on the virtualenv project itself[1], a quick solution is to revert to the also common `/usr/bin/env python` way of pointing to the Python interpreter. [1] - https://github.com/pypa/virtualenv/issues/124Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 05 12月, 2015 3 次提交
-
-
由 Lukáš Doktor 提交于
Fix test providers checkout
-
由 Olav Philipp Henschel 提交于
-
由 Olav Philipp Henschel 提交于
Var "lbranch" was hard coded to "master", so it was never copied from var "branch".
-
- 03 12月, 2015 7 次提交
-
-
由 Cleber Rosa 提交于
-
由 Olav Philipp Henschel 提交于
"make check" needs pydot to run.
-
由 Lukáš Doktor 提交于
We used to support subtests filter to load only some of the avocado tests, but the functionality is broken. This patch brings this functionality back. It uses "re.search" so people can use partial matches. Additionally it includes selftests to prevent future breakages. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
This patch adds unittest for loading simple tests with arguments. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
requirements-travis.txt: Require inspektor 0.2.0
-
由 Lucas Meneghel Rodrigues 提交于
Inspektor 0.2.0 has some improvements in the queue, mainly now by default we are going to start being picky on unused imports. Which is something I wanted to do for a long time. Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>
-
- 02 12月, 2015 4 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
avocado: Fixing unused imports
-
由 Lucas Meneghel Rodrigues 提交于
This was caught by modified inspektor check. I'm still working on inspektor, meanwhile let's send this fix. Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>
-
由 Lukáš Doktor 提交于
When the test process exits before the deadline, it raises exception while trying to destroy it. Let's just ignore the OSError and proceed. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
Currently the test status was only updated on `TestStatus.check` method, which was also used in `TestStatus.abort`. But the meaning of `check` return is whether the job was interrupted. It does not mean the status is valid, which in some cases might have reported the test status `None`. This patch reworks the way we interact with `TestStatus`. It contains `interrupt` variable, which means the test was interrupted and we should leave the execution. It still have the `status` variable, which contains the status, but now those two variables are automatically updated on query (using __getattribute__). Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 01 12月, 2015 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
requirements-travis.txt: Fix inspektor requirement problems
-
由 Lucas Meneghel Rodrigues 提交于
Require inspektor 0.1.19 to fix the pylint requirement problems on python 2.6. Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>
-
- 28 11月, 2015 2 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
avocado.utils.process: Improve detection to run cmd in GDB [v2]
-
由 Lukáš Doktor 提交于
shlex.split() can fail on some strange commands (eg. on an unfinished quotation). This patch fallbacks to simple string.split() in such cases, which might return incorrect results, but is safer to use. Although it logs warning about this notifying the user about possible issue. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-