Re: [PATCH 2/3] avocado_qemu: add AVOCADO_DEFAULT_ARCH for cross-arch tests

2023-01-18 Thread Daniel Henrique Barboza
On 1/18/23 12:23, Fabiano Rosas wrote: Daniel Henrique Barboza writes: All avocado tests that are arch agnostic (i.e. does not set an 'arch' tag) are run with arch=None in pick_default_qemu_bin(), and then 'arch' is set to os.uname()[4], meaning that it will take the arch of the running hos

Re: [PATCH 2/3] avocado_qemu: add AVOCADO_DEFAULT_ARCH for cross-arch tests

2023-01-18 Thread Fabiano Rosas
Daniel Henrique Barboza writes: > All avocado tests that are arch agnostic (i.e. does not set an 'arch' > tag) are run with arch=None in pick_default_qemu_bin(), and then 'arch' > is set to os.uname()[4], meaning that it will take the arch of the > running host. > > This means that if one compile

[PATCH 2/3] avocado_qemu: add AVOCADO_DEFAULT_ARCH for cross-arch tests

2023-01-18 Thread Daniel Henrique Barboza
All avocado tests that are arch agnostic (i.e. does not set an 'arch' tag) are run with arch=None in pick_default_qemu_bin(), and then 'arch' is set to os.uname()[4], meaning that it will take the arch of the running host. This means that if one compiles QEMU binaries for non-x86 targets on an x86