Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnected test execution #5862

Open
richtja opened this issue Feb 2, 2024 · 0 comments
Open

Disconnected test execution #5862

richtja opened this issue Feb 2, 2024 · 0 comments

Comments

@richtja
Copy link
Contributor

richtja commented Feb 2, 2024

Is your feature request related to a problem? Please describe.

One of the key features of nrunner architecture should be disconnected test execution. But how the #5794 this feature is still not supported. Right now, the tasks need to communicate with avocado's status server all the time during the task execution. The goal of this feature is to start a task in the spawner's environment and then disconnect from it, and when the task is finished gather logs and results.

This feature will be useful when connection to the spawner's environments is not stable or too expensive to keep it during the whole execution.

Describe the solution you'd like
Let's introduce new Task config variable local_log_dir. This variable will be set by spawner before the Task is executed. When this variable is set, the Task will store any runtime messages to this file to preserve all task runtime information inside the spawner environment to be retrieved by the spawner any time when it is needed.

@mr-avocado mr-avocado bot moved this to Triage in Default project Feb 2, 2024
@richtja richtja moved this from Triage to Long Term (Next Q) Backlog in Default project Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Long Term (Next Q) Backlog
Development

No branches or pull requests

1 participant