This plugin makes use of remote aexpect sessions (to remote hosts or equivalently remote containers behind remote hosts forwarded via specific ports) as slots to schedule test runs on.
It mainly draws inspiration and mimics slot and other code from the LXC spawner with the exception of extra configurable test timeout that is enforced by aexpect as a dependency and fully specific to this type of spawner.
To install the Remote Spawner plugin from pip, use:
$ sudo pip install avocado-framework-plugin-spawner-remote
After it is installed, add a slot (e.g. “board”) to your avocado config file:
[spawner.remote] slots = ['board']
Then you need a JSON file of the same name as the slot. Its contents are the command line parameters of aexpect’s remote_login function of module remote, e.g.:
{
"client": "telnet",
"host": "192.168.64.2",
"port": "23",
"username": "root",
"password": "",
"prompt": "#"
}
Final important detail: the remote site also needs avocado installed.
Metadata
Release files for avocado-framework-plugin-spawner-remote 113.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| avocado_framework_plugin_spawner_remote-113.0.tar.gz | 5.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| avocado_framework_plugin_spawner_remote-113.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.2 kB
Release files / avocado_framework_plugin_spawner_remote-113.0.tar.gz
| Download URL | avocado_framework_plugin_spawner_remote-113.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d21ea03df91fcdf92272724ccd16ca49d2af4c39a50a5be5dffe321208a975f
|
|
BLAKE2b-256 checksum How to use checksums |
36ccee5ed66617c5a639b2e3e8267a495ffa69a7c47054605b8aae3ca71e0c13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.
Transparency logRelease files / avocado_framework_plugin_spawner_remote-113.0-py3-none-any.whl
| Download URL | avocado_framework_plugin_spawner_remote-113.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ebc5c1feeeeed485763ff538bfbee33487107343956814bb404969869f31b80
|
|
BLAKE2b-256 checksum How to use checksums |
e56610d694f20d43946dbc35861524768bb3a6af5951bbaf27917da35dada0c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 26, 2026.
Transparency log