I've followed the official guide[1].

[1]: https://github.com/aspect-build/rules_lint/blob/f1645be8eca5deebe0750c8cfa295adc58c256c1/docs/formatting.md

It's needed to make `attr.ib` work correctly.

This is the correct fix for 217cd09c.

This allows running all end-to-end tests hermetically, both locally and
in CI. The `e2e/docker` folder is left as an example of how to integrate
`rules_labgrid` with Docker, and should only be run manually.

This allows running the workflows (e.g. `labgrid_genrule`) against the
host machine.

Previously, we were registering the QEMU toolchain against any AMD64
Linux, which would select that toolchain if running one of the workflows
(e.g. `labgrid_genrule`) without specifying a platform. We now require
consumers to opt-in to using QEMU by using the constraint
`@rules_labgrid//constraint/emulator:qemu`.

The new constraint lives under a new top-level directory, as it's not
specific to `rules_labgrid` and could be extracted into a separate
module in the future.

Alex Tercete authored Nov 07, 2024 and Idan Saadon committed Nov 07, 2024

This introduces a `labgrid_test` rule, which allows running a test executable on the device (`:inner` can be any `*_binary` target):

```
labgrid_test(
    name = "example",
    src = ":inner",
    platform = ":platform",
)
```

It integrates with Bazel XML reporting functionality by writing to `${XML_OUTPUT_FILE}` on the host, if a XML report is generated on the device.

I've left a few `FIXME`'s which will be addressed in follow-up MRs.

Use a dot-separated `dest` attribute so that the `Namespace` destination
and the `State` destination can be described.

The `dest` can then be used within the `Action` constructor
to set the default value.

This makes `State` read-only as well.

Consumers who want to wrap the `//labgrid/executor` as an executable
rule can now root-symlink an `extra.args` file with args to be passed to
the executor.

Now that we're using `@ape` tools in `//labgrid/run`, we need to specify
a CPU explicitly in our platform definiton.

Simplifies the remote setup by removing an unnecessary `tools`
directory.

Idan Saadon authored Oct 30, 2024 and Matthew Clarkson committed Oct 30, 2024

The remote execution root should be isolated from any other executions.

It should be cleaned up at the end of the execution.

`@ape//:*` targets are deprecated.

They are now baked into the executor, no need to expose them to other packages.

`//labgrid/executor` now reads the arguments from runfiles and passes them into the `ArgumentParser`.

This simplifies the usage in downstream rules: they no longer have to depend on the executor `args` and pass them into the action arguments.

Matthew Clarkson authored Oct 24, 2024 and Alex Tercete committed Oct 25, 2024

QEMU attempts to write copy-on-write snapshots to `/var/tmp` because
they can be become large and `/tmp` is often `tmpfs` which may
not have enough space.

`/var/tmp` in a sandbox is read-only. This changes QEMU
to write into `./tmp` which is relative to the sandbox
root.

Matthew Clarkson authored Oct 24, 2024 and Alex Tercete committed Oct 25, 2024

Needed for `bazelisk run` to respect `env`.

Matthew Clarkson authored Oct 25, 2024 and Alex Tercete committed Oct 25, 2024

If the user provides `TMPDIR`, make sure it is created.

Matthew Clarkson authored Oct 23, 2024 and Alex Tercete committed Oct 25, 2024

Allows the environment variables to propagate through Bazel run targets.

Allows any Bazel `semantic-release` plugins to have optimal environment.

Allows identifying rules that require a valid Docker daemon
to be setup.