Hi Cleber, Lukáš,
On 8/29/19 11:24 AM, Philippe Mathieu-Daudé wrote:
> On 8/29/19 5:27 AM, Cleber Rosa wrote:
>> On Thu, Aug 29, 2019 at 11:51:17AM +1000, David Gibson wrote:
[...]
>>> Fwiw, I also get an equally cryptic error that I haven't figured out
>>> the cause for on my 32-bit Fedora container environment:
>>>
>>> VENV /home/dwg/src/qemu/build/i386/tests/venv
>>> PIP /home/dwg/src/qemu/tests/requirements.txt
>>> Failed building wheel for bcrypt
>>> Could not build wheels for bcrypt which use PEP 517 and cannot be installed
>>> directly
>>> You are using pip version 19.0.3, however version 19.2.3 is available.
>>> You should consider upgrading via the 'pip install --upgrade pip' command.
>>>
>>
>> This is certainly caused by pip not being able to install paramiko on
>> those systems. I have dealt with paramiko (and its many dependencies)
>> before on the avocado remote runner plugin (which is not being used
>> here) and it was not fun.
>>
>> My personal goal was to rely on the ssh binary as an ssh client, which
>> should be more ubiquitous, and with that I added a simple wrapper to
>> Avocado:
>>
>>
>> https://avocado-framework.readthedocs.io/en/71.0/api/utils/avocado.utils.html#module-avocado.utils.ssh
>
> I did not know this module.
class avocado.utils.ssh.Session(address, credentials)
Parameters:
credentials (tuple)
username and path to a key for authentication purposes
The current test uses username + password.
Can we use this credentials with the Avocado module?
(The image used is prebuilt).
>> I guess we should consider changing the (few) tests that require
>> paramiko to use that module instead.
>
> Clean way to resolve this issue.
