- 22 2月, 2018 12 次提交
-
-
由 Cleber Rosa 提交于
The config file generated and used on this test was missing a separator between the section name and the first key/value line. This adds a new line and makes the resulting file aesthetically pleasing and able to be parsed. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com> * https://github.com/avocado-framework/avocado: avocado/utils/kernel.py: support other major versions of the Linux kernel
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com> * https://github.com/avocado-framework/avocado: JSON Result Plugin: remove legacy (duplicated) fields
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com> * https://github.com/avocado-framework/avocado: DummyLoader: move it out of core
-
由 Cleber Rosa 提交于
This loader is supposed to not perform anything locally, and it's actually a hack to bypass the loader when tests are to be resolved and run remotely. Its only users is the remote runner. To avoid pollution in core, let's move it to that module. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Currently we have hardcoded the version 3 series in the URL used to fetch the source code. Let's use the major version, from the full version number, as the URL prefix instead of the hardcoded "3.x". Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The "url" and "test" fields are just legacy and duplicated fields that carry the same data as the "id" field. Let's remove those. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 17 2月, 2018 13 次提交
-
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com> * https://github.com/avocado-framework/avocado: avocado/core/parser.py: remove legacy default_avocado_params Makefile: remove cleanup of eggs generated on 36lts Travis-CI: remove 36lts branch from automated tests avocado.utils.make: drop legacy interface avocado/utils/build.py: fix docstring varianter: remove _process_default_params() method varianter: remove compatiblity code for 36lts mux: remove _get_variant_ids() method mux: remove compatiblity code for 36lts
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
From the args that are given to the Avocado test runner. They were used on 36lts, but now with its EOL, we can remove it. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The Avocado module named used to be simply "avocado", and thus, those versions would produce "egg-info"s with that name. Now with 36lts EOLed, we can ignore that. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Now that 36lts is EOLed, let's remove it from Travis-CI. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The notes on this module seems to suggest that only the `run_make` interface needs to be changed, and `make` should remain AS IS. This implements this understanding, limiting the changes to the more commonly used `make` interface. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Let's add the missing docstring info on `path` and `ignore_status`, and fix the parameter `extra_args` name. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Because it's only used once, so let's inline it. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
With 36lts End of Life, we can remove compatibility code. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Because it's only used once, so let's inline it. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
With 36lts End of Life, we can remove compatibility code. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 16 2月, 2018 9 次提交
-
-
由 Lukáš Doktor 提交于
TAP does not defines WARN(ing) test status, but allows comments. Let's simply note the test finished with some warnings which is better than nothing. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
TAP does not defines nor knows about "CANCEL" test status, it only defines "SKIP" and "TODO". Let's map the "CANCEL" test status to "SKIP" to comply with the specification. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Cleber Rosa 提交于
Which adds the namespace of the function that created the class. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Which is OK under Python 2, but not under Python 3. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
When the xunit plugin is writing to the stdout, we don't want a representation of bytes, but the bytes encoded as a string users can read. We're sticking to the 'UTF-8' encoding here because it's already hard coded here in the document (as opposed to the encoding the user may have set to its stdout). Before this patch, `avocado run /bin/false --xunit -` results in: b'<?xml version="1.0" encoding="UTF-8"?>\n<testsuite errors="0" failures="0" name="avocado" skipped="0" tests="1" time="0.018056154251098633" timestamp="2018-02-13 12:34:55.627077">\n\t<testcase classname="SimpleTest" name="1-/bin/true" time="0.018056154251098633"/>\n</testsuite>\n' After this patch it becomes: <?xml version="1.0" encoding="UTF-8"?> <testsuite errors="0" failures="0" name="avocado" skipped="0" tests="1" time="0.018121719360351562" timestamp="2018-02-13 12:34:15.669379"> <testcase classname="SimpleTest" name="1-/bin/true" time="0.018121719360351562"/> </testsuite> Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
On Python 3, it's not possible to create Elements detached from a Document. The following code fails (later than it should) on Python 3: >>> from xml.dom.minidom import Element >>> e = Element('foo') >>> e.setAttribute('bar', 'baz') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python3.6/xml/dom/minidom.py", line 741, in setAttribute attr.ownerDocument = self.ownerDocument AttributeError: ownerDocument Let's create elements within the document, with the `createElement` API. According to the docs "The element is not inserted into the document when it is created", so the (unchanged) code that actually puts the element in the right place still applies. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The avocado.utils.process module has been changed so that the content of stdout and stderr are now bytes. The content generated by the iso9660 backend implementations should also operate on bytes, given that it makes little sense for the library to assume a given content type of a file (inside an iso9660 archive). To make the data returned by the various backend `read()` implementations always return bytes on both Python 2 and 3, an explicit conversion is done from strings to bytes (which affects only Python 2, since Python 3 already operates with bytes on files opened in binary mode). Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This brings a change in behaviour, in which the stdout/stderr of the executed process will now be of bytes type, instead of a string type. Two new attributes, which are implemented as properties, have been added to the CmdResult class, `stdout_text` and `stderr_text`. Those are convenience methods that will return the same content that is in `stdout` and `stderr`, reespectively, but decoded on the fly[1]. With regards to encoding, if one is not provided, the result of `sys.getdefaultencoding()` will be used ("utf-8" for Python 3 and "ascii" for Python 2). Applications and/or tests using the APIs that return a CmdResult should, to the best of my knowledge, set a default encoding themselves so a stable behavior across Python versions. But that if left to users of this API. A different tradeoff/design decision has to do with the tests modified here. One option is to have "text" (as in sequences of human readable glyphs) as being of Python type "str". On Python 2, "str" can be compared to "bytes" because a conversion will happen on demand. That is, the following is fine on Python 2: >>> result = process.run("command") >>> "expected" in process.stdout Where `expected` is of type "str" and `process.stdout` is of type "bytes". This is not true of Python 3, so either the types must match or a conversion must be done explicitly. The solutions to that are: 1) have these "text" as (of type) "bytes" in the source code itself, and avoid the conversion whenever possible 2) have "strings" in the source code itself, and use the conversion provided by `CmdResult.stdout_text` and `CmdResult.stderr_text`. The approach chosen here is to avoid conversion if possible, that is, use "byte" types, given the fact that the source code encoding is by default 'ascii' and most of the "text" dealt with here can be represented in 'ascii' too. This is equivalent of doing: result = process.run("command") b"expected" in process.stdout "errors: %s" % 0 in process.stderr_text [1] The obvious alternative, instead of decoding these on the fly would be to have multiple copies of the "same" data. This assumes that binary data produced on the stdout/stderr will usually be larger than textual data. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 15 2月, 2018 6 次提交
-
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Cleber Rosa 提交于
Which makes data comparison predictable and stable across Python versions and encodings. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Before the external runner had this name, it was named "inner runner", and the sentence logged made sense like this: "Running test with the inner level test runner /bin/foobar" With the name change to "external" using "level" here doesn't sound right anymore. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This is similar to the xunit unittest changes in 353fed04, but now applied to the functional tests which happen to use the same features. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This is similar to the change in 418bf92a, but now applied to the functional tests that deal with xunit. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-