Contributing a self-hosted hardware runner for community HIL testing

[maxxlife]

Summary

does zephyr has self-hosted testing runner? i have a bunch of zephyr-supported hardware, and smal nuc, that could utilize to run tests to benefit community. any documentation regarding that?

Describe the solution you'd like

I have a small NUC and a variety of Zephyr-supported hardware boards. I would love to utilize this setup to run automated Hardware-in-the-Loop (HIL) tests to benefit the Zephyr community.

Does the Zephyr project currently have a framework or infrastructure to accept community-contributed, self-hosted test runners?

I am aware that attaching self-hosted runners directly to a public GitHub repository carries security risks (regarding malicious PRs executing arbitrary code), but I wanted to ask:
Is there an existing federated hardware lab, or any documentation on how community members can safely contribute physical hardware for testing?
Is there a preferred way to hook up a remote runner to execute twister on nightly builds or release candidates?

I'd be happy to dedicate this hardware to the project if there is a safe and beneficial way to do so. Please point me in the right direction!

Alternatives

No response

Additional Context

No response

[JarmouniA]

Cc @teburd

[teburd]

The way I am doing this is with a script that looks at PRs for labels. Then tests that PR against my boards. I have some cleanup to do before posting this. It also turns out reporting results in a github comment is pretty limiting.

[maxxlife]

The way I am doing this is with a script that looks at PRs for labels. Then tests that PR against my boards. I have some cleanup to do before posting this. It also turns out reporting results in a github comment is pretty limiting.

Okay, let's keep in touch. I will join Testing WG meeting this week March 26th.

[maxxlife]

The way I am doing this is with a script that looks at PRs for labels. Then tests that PR against my boards. I have some cleanup to do before posting this. It also turns out reporting results in a github comment is pretty limiting.

Let me know if you need help with the cleanup, running private tests, or anything else like that.

[github-actions]

This issue has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 7 days. Note, that you can always re-open a closed issue at any time.