This makes it possible to use pre-built test binaries.

This allows saving the remote path of a file provided under `data` in an
environment variable for later use within `src`.

This works for simple cases, but it doesn't support advanced scenarios
as path mapping isn't robust yet.

By adding the `data` files to the existing runfiles directory of `src`,
they are automatically transferred to the device.

Jordan Bonser authored Apr 15, 2025 and Alex Tercete committed Apr 16, 2025

the local harness was only usable as a context manager.
this commit adds a new target:

`bazelisk run //bazel/labgrid/local:harness`

this makes the harness available as a standalone program, which sets
up a dummy place and tags for it to be used by the labgrid client.

the harness chooses a free port on the machine and outputs its url
to stdout.

the program is terminated  using keyboard interrupt.

Jordan Bonser authored Apr 15, 2025 and Alex Tercete committed Apr 16, 2025

make use of the local harness to run tests against
the acquire and reserve context managers.

use the new target:
`bazelisk test //bazel/labgrid/manager:test`

Jordan Bonser authored Apr 02, 2025 and Alex Tercete committed Apr 15, 2025

the coordinator/harness/exporter packages have been
refactored to support the new gRPC coordinator approach
that is now being taken in the `Labgrid` project.

The handling of the subprocess calls has been simplified
and there are a number of changes to support the new output
and parameters that can be provided to the coordinator and
exporter.

The harness test has also been tweaked to allow it to test
the functionality correctly.

large portions of the crossbar related functionality is also
removed as it is no longer necessary along with the additional
requirements and python pip related code.

Jordan Bonser authored Apr 02, 2025 and Alex Tercete committed Apr 15, 2025

crossbar is no longer supported by `Labgrid` and
a different coordinator implementation is going to
be used so this commit renames the crossbar package
to make way for an easier refactoring to a different
coordinator.

BREAKING CHANGE: `crossbar` renamed to `coordinator`

Jordan Bonser authored Apr 02, 2025 and Alex Tercete committed Apr 15, 2025

the coordinator/crossbar combination of names was a bit
misleading as crossbar was the coordinator and in fact the
coordinator package was a harness that combined the local
coordinator and exporter as a context manager to be used in
other code. This refactor makes that distinction more obvious
and also paves the way for the renaming of crossbar to
coordinator as crossbar is no longer supported in `Labgrid`

BREAKING CHANGE: `coordinator` renamed to `harness`

Jordan Bonser authored Mar 28, 2025 and Alex Tercete committed Apr 15, 2025

the mock folder has now been renamed to local as the coordinator,
exporter and client code is actually ran as opposed to having
that functionality being mocked.

BREAKING CHANGE: `mock` folder renamed to `local`

Recent changes to `labgrid_test` has caused `stardoc` to start failing
due to missing `bzl_library` targets in newly added dependencies.

This delegates most responsibilities to the rule the macro is wrapping,
which is what we want.

This is the recommended way to implement macros, and makes
`labgrid_config` easier to use in isolation.

BREAKING CHANGE:
`@rules_labgrid//labgrid/constraint/device:configurable` has been
renamed to `@rules_labgrid//labgrid/constraint/device:ssh`

Creates Tool and Tools classes to abstract usage of tools.

By doing it only for strategy state changes, we ensure that the
`runfiles` library can find runfiles from anywhere within `runner`.

By default, `subprocess.run` captures the environment variables from the
host process and passes it to the subprocess. This causes issues when
the subprocess needs to access its own runfiles.

These two managers can be passed to a `labgrid_config_toolchain`
to allow the toolchain to use Labgrid's reserve and acquire
functionality to gain allocation of a place before running
the test binary, then finally releasing it once the test
has completed.

allowing its use with the upcoming reserve and
acquire managers. it provides some default error
handling and options to handle yaml or str output.

the base context manager for the executor was confusingly
named executor, this commit moves that to the `manager`
folder in preparation to add new managers.

BREAKING CHANGE: manager moved and renamed from executor to manager

This makes the contents `run` very readable.