Cleber Rosa

This may become easier once we have better module testing. Expecting such testing features to be part of the autils effort. Until then, I'm closing this issue as this is...

In order to move this issue forward, I'll attempt to run the e2dk tests (and examples given in the issue description) with the podman spawner.

While this is a worthy goal, the list of options is outdated given the age of this issue. I'm closing this, and we can consider opening a similar one in...

> I met the same issue while running QEMU (latest git) tests with `make check-avocado` on macOS 13.2 ARM64 with Python 3.11. Same place as well: > > ``` >...

> @clebergnu I did the clean way (1st option) and most avocado tests passed just fine: Thanks for testing it, this is great news! > > ``` > (41/69) tests/avocado/machine_aspeed.py:AST2x00MachineSDK.test_arm_ast2500_evb_sdk:...

This is an issue only with the so-called "legacy" runner, which is no longer available. "nrunner", the current architecture, should not be susceptible to this. Feel free to reopen this...

I consider this a feature request. Adding the appropriate labels.

The loaders are not even a valid concept/component anymore, so let's close this issue.

Closing in favor of #5113

Based on the last comment (and the lack of response), I'm assuming this issue is no longer valid. Also, for remote test execution the [remote spawner](https://avocado-framework.readthedocs.io/en/103.0/plugins/optional/spawner_remote.html) is a possibility now.