On 8/1/19 9:24 AM, Daniel Henrique Barboza wrote: >>> >>> So I think the difference is that your dev box is not echoing the >>> commands, and the real problem is that the test is dependent on the >>> current environment (is there some configuration file that determines >>> whether virsh in batch mode will echo what is typed?) >> I'll see if I can get different results running the tests in a Power >> 8/9 server. >> I'll also do a clean 'git clone' run to see if the results differ. >> > > Tested with a fresh git clone on my dev box, a Power 8 server and a Power 9 > server. The result is the same: Do you have some file under ~/.config/libvirt, or maybe contents in ~/.inputrc, or some similar problem that is being pulled in regardless of your build setup? Would an strace prove what file is getting opened outside of the control of the test, where we need to fix our sanitization to avoid the test depending on your home directory? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
