Cleber Rosa

Looks like this is an easy fix: ```diff diff --git a/scripts/external_runner.py b/scripts/external_runner.py index 50b8ca29f..441966e22 100755 --- a/scripts/external_runner.py +++ b/scripts/external_runner.py @@ -29,7 +29,7 @@ import argparse import sys from avocado.core.job import...

> > We made sure `nrunner` works fine with the QEMU tests. I'm about to send a patch series bumping Avocado in QEMU to the latest release (99.0). > >...

The legacy runner and loader have been completely removed, so the main topic issue here is resolved. Issue #3882 is *related* but not a requirement of this issue.

The legacy runner and loader are completely removed at this point. A feature that was not brought over to nrunner yet is the "output check" feature. Issue https://github.com/avocado-framework/avocado/issues/3882 tracks that.

Closing this issue for now, due to change in priorities.

I'll re-evaluate this in terms of latest Avocado and QEMU.

I tested #5788 to the limits, and it solves this issue AFAICT. @pevogam if you think we have issues with the LXC Spawner, adding the option to `destroy()` the container,...

I have a BluePrint under development that will propose this feature under the new Avocado architecture (nrunner). Stay tuned!

@marioaag, we are trying to have a better understanding of your use case. Are you suggesting that you expect to have a runnable, such as the one that would begenerated...

This feature has not been demanded in ~ months. Closing it.