This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/82
** Changed in: qemu
Status: New => Expired
** Bug watch
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1874674
Title:
[Feature request] acceptance test class to run user-mode binaries
Status in QEMU:
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1874674
Title:
[Feature request] acceptance test class to run user-mode binaries
Status in QE
On 4/24/20 9:14 PM, Richard Henderson wrote:
> What user-mode testing do you think might be improved by using avocado?
Test unmodified real-world binaries, know to work in the field.
Test can be added by users without having to be a TCG developer, see
https://www.mail-archive.com/qemu-devel@nongn
What user-mode testing do you think might be improved by using avocado?
IMO at present we have a fairly comprehensive testing infrastructure for
user-mode that is simply underused. With docker, we have a set of
cross-compilers for most guest architectures, and we are able to build
statically link
