- 09 3月, 2018 2 次提交
-
-
由 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: Remove deprecated multiplex options
-
- 08 3月, 2018 5 次提交
-
-
由 Cleber Rosa 提交于
The '--filter-{only,out}' and '--multiplex' options have been deprecated in favor of '--mux-filter-{only,out}' and '--mux-yaml'. Let's remove them for good. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
To avoid breakage when newer versions come out, let's pin to current GitHub API version to v3. Reference: https://developer.github.com/v3/media/#request-specific-versionSigned-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Amador Pahim 提交于
There's a new DataSize object in avocado.utils.datastructures. Let's remove the redundant code and just use the DataSize object. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Now that we have a second use case for it, let's finally create the DataSize object. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
- 06 3月, 2018 1 次提交
-
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
- 01 3月, 2018 2 次提交
-
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 28 2月, 2018 3 次提交
-
-
由 Junxiang Li 提交于
To fix the pip 9.0.1 install python requirements with ">=2.7, >=3.4" failure, ">=2.7, >=3.4" means ">=2.7" and ">=3.4", so the result is ">=3.4" for reference: https://stackoverflow.com/questions/44660448/Signed-off-by: NJunxiang Li <junli@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
- 27 2月, 2018 13 次提交
-
-
由 Cleber Rosa 提交于
We are, finally, advertising Python 3 support. Yes, it's supposed to be "beta" quality level, as there are a few leftover issues we know about, and possibly a whole lot more we don't. Still, we're taking that leap of faith, and that suggests describing that so that PyPI users and installation tools know about it. Reference: https://packaging.python.org/tutorials/distributing-packages/#classifiers Reference: https://packaging.python.org/tutorials/distributing-packages/#python-requiresSigned-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The API used to get the file, by name, is `get_data()`, which looks for that file in one of the data directories that the class provides (file-level, class-level, variant-level, etc). Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
These parameters are not class instantiation parameters, which is the indentend usage of those docstring notations. But, even worse, they don't exist in these example tests at all. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
We don't do Python 2.6 anymore, so it's safe to drop this workaround. 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>
-
由 Amador Pahim 提交于
The "test" fields was removed from JSON output as it was legacy/duplicated. This patch adapts the remote runner accordingly, using the key "id" instead. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
As part of the v59 release process. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Now there's a new parameter executable to use as the commandline information. The previous parameter, name can now be hijacked by the yaml_loader, making this plugin to break. This patch adapts to that change of internal API. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Now there's a new parameter `executable` to use as the command line information. The previous parameter, `name` can now be hijacked by the yaml_loader, making this plugin to break. This patch adapts to that change of internal API. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Now there's a new parameter `executable` to use as the command line information. The previous parameter, `name` can now be hijacked by the yaml_loader, making this plugin to break. This patch adapts to that change of internal API. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
- 26 2月, 2018 14 次提交
-
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Amador Pahim 提交于
This check was introduced in the previous draft of this plugin, when it was using gtester, and left over. Dropping. Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Harish 提交于
As reported in the following link: https://github.com/avocado-framework/avocado/issues/2476 build.run_make fails to run when used without any argument. This patch handles the failure and runs make with ncpus if it is not specified in "env" Signed-off-by: NHarish <harish@linux.vnet.ibm.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Amador Pahim 提交于
Signed-off-by: NAmador Pahim <apahim@redhat.com>
-
由 Cleber Rosa 提交于
The current code style creates and appends an object into the list, and then later implicitly references that item using the `[-1]` notation, changing its filter. While correct, IMO, it's easier to follow code that creates the object, sets its values, and then appends it to the list. This was a style only change that appeared while debugging another mux related issue. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
When things go wrong, the Avocado command line app will write a file with the backtrace that caused the trash. Depending on its content, it may not be possible to encode that in an file encoded as ASCII. Let's default to utf-8 then. Also, this is done for portability reasons, as it brings a consistent behavior (one explicit encoding type) across Python 2 and 3, which have different default encodings. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
On Python 3, trying to copy a FilterSet, using the instance.copy() method, will return a plain set() object. This influences a number of code, including the fingerprint generation, and the variant ID which will be based on the hash of the fingerprint. Let's make things predictable and copy using Python's standard module copy. This fixes the functional test in module `test_getdata` under Python 3, as the variant IDs are now the same on jobs run under Python 2 and 3. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Since system_output() returns bytes (from CmdResult.stdout), the split operation should also be done with bytes. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
In situations where a user of the CmdResult class manually sets the stdout/stderr attributes to a string, instead of the recommended and documented content of type "bytes", it won't be possible to "decode" the bytes into a string of a given encoding, and we'll end up with a crash. Since the goal of std{out,err}_text is to return a text version of stdout, if itself already is of such a type, let's just return it. Additionally, if the data cannot be "decode()d", let's raise an explicit TypeError on this location, rather than later in the code when its value is attempted to be used. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Commit 7d0e6a44 effectively changed the supposed value of stdout and stderr attributes to being of type "bytes". But, the parameters with the same names, and their defaults values was not updated. Let's make stdout and stderr into bytes by default, both the parameters and attribute values when no other is given. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-