- 12 12月, 2018 10 次提交
-
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
This change introduces two new utility functions related with filesystems. One function returns all filesystem types supported by the running kernel and the other returns the filesystem type of a given mount point. Signed-off-by: NPraveen K Pandey <praveen@linux.vnet.ibm.com> Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Praveen K Pandey 提交于
added utility which takes as argument a file and pattern and return true or false respectively when pattern matches in file or not >>> from avocado.utils import genio >>> genio.find_pattern("/home/praveen/file1", "praveen") True >>> genio.find_pattern("/home/praveen/file1", "Praveen") False >>> genio.find_pattern("/home/praveen/file12", "Praveen") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "avocado/utils/genio.py", line 219, in find_pattern % (filename, pattern)) avocado.utils.genio.GenIOError: invalid file /home/praveen/file12 to match pattern Praveen >>> Signed-off-by: NPraveen K Pandey <praveen@linux.vnet.ibm.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
Previous recursive implementation of waiting for children is not really possible, because parent has to treat the children exit, otherwise we get temporary zombie status until the parent process is resumed. This implementation also uses recursive way of killing the children, but instead of waiting for them to die it reports the killed processes and only in the main function it resumes all of them and watches them to die. As a benefit people might now get list of killed processes as return. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 11 12月, 2018 3 次提交
-
-
由 Cleber Rosa 提交于
We now need to use jinja2 packages, instead of pystache. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
We only render HTML, that is, we never render anything that must not have any content escaped. So, let's always enable the autoescape feature. This fixes the issue with jinja2 version 2.7.2, available on EL 7, that has the autoescape parameter to environments, but doesn't have the select_autoescape() utility function for selecting what to escape automatically. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 10 12月, 2018 1 次提交
-
-
由 Caio Carrara 提交于
Since the pystache project seems to be dead, without recent updates and has not support planned for Python 3.7+, this change replace it by jinja template engine. Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
- 08 12月, 2018 11 次提交
-
-
由 Cleber Rosa 提交于
To a class that doesn't share the same setup requirements as the other tag filtering tests, but it's still tag filtering related. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
To the previously created TagFilter test class, as it shares the same setUp requirements. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Into smaller tests that are hopefully easier to read and, if it occurs, much easier to understand the failure. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This lint exception is no longer necessary, let's remove it. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This seems to be a leftover, and is not used anywhere. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This is causing a lot of ResourceWarnings, specially when running the selftests. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
The new template structure is based on Jinja template engine. Besides the template statements itself it was also split the js and css code in proper separated files. This way the results template keeps simpler. Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
It's a common use case to want to make sure a file can be read, or if not fail as early as possible with a relevant error message. The avocado.utils.iso9600 is doing that itself, but for the sake of being useful to a wider audience, let's make that a utility itself. As always, the benefits are also increased test coverage and documentation. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 07 12月, 2018 10 次提交
-
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Caio Carrara 提交于
Currently to generate the HTML report the success rate of a test result is computed by the plugin itself. Since this is an information about the test result it should be calculated by the Result object and no anywhere else. This change adds the rate property to Result class according with the code (method) already in place in HTML plugin. This new property will be used soon when the new template engine be added to HTML plugin. Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
The try/except block around the execution of apt-file to update is pointless if we're ignoring the status of the apt-file command. I'll defer to a later moment the discussion on whether this failure should be fatal, and not just log its failure. That is currently covered by the fact that the "apt-file search <path>" execution will fail with non-zero status when the cache is empty (that is, when apt-file update was not executed successfully). Also, add a test that checks the behavior of the affected method. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This fixes the backends usage on Python 3. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
While testing on a "debian:latest" (9.6) container, I've found that detection was broken, because the "debian version" file slightly changed names. While at it, let's get the version from that file. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
In an effort to make jobs more self contained, and given that dry-run jobs created temporary content that is not supposed to be kept after the job is run, this introduces the following changes: * Jobs with "dry-run" enabled will now, by default, cleanup their own data. Basically, this means that the "base log directory" created during job initialization, and that for non "dry-run" jobs is usually "~/avocado/job-results", will also be removed at the job's "cleanup()" phase. * A new "--dry-run-no-cleanup" command line option, that only makes sense when jobs with dry-run enabled start to clean up data for themselves * Because some result plugins will, by default, write to the job results directory, results plugins are now run before a job cleanup is done. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
By making it inherit from object instead, now that all children classes are boiler-plate free and all setup a "iso" attribute, we can remove the check and make only them (children classes) inherit from unittest.TestCase. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
As per the last change, let's move the test into the base class, and just check if the ISO has been setup for this test to work with, and if not, skip it. This removes a lot of the boiler plate code. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 06 12月, 2018 5 次提交
-
-
由 Cleber Rosa 提交于
The division of responsiblities in the ISO9660 test classes is one that, because the children classes need to setup the "iso" instance, the "mnt_dir_worflow" is not named as a method that is considered a test in the base class. The problems with that are: 1) a lot of boiler plate code in the children classes just to call the "mnt_dir_workflow" method. 2) skip*() decorators do not work in generic methods. To simplify issue 1, and fix 2, let's rename that method to become a test method, and just add a condition that, unless "self.iso" is prepared, the test is going to be skipped. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Lukáš Doktor 提交于
When using the "process.kill_process_tree" it might be useful to wait for all of the pids to die. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-