| commit | ff8e7a4387af2ab8aec26e51bc3eef3a292bbbb0 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jul 24 12:16:16 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jul 24 20:20:13 2025 +0000 |
| tree | 206e43bc02250ca86c92ef3cee672bf337d3c7c6 | |
| parent | d713349effab8e72727478c92ac75723a451ae72 [diff] |
unit-test: require meson 1.3.0 for relative_to calls
Meson can give the following warning:
```
WARNING: Project specifies a minimum meson_version '>=1.1.1' but uses features which were added in newer versions:
* 1.3.0: {'fs.relative_to'}
```
Catch this in our CI.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I852950bfc7b02abae9d00fb5663136cfdc690736
Build script for CI jobs in Jenkins.
Formatting linters sometimes change stylistic output across releases. Separately, some linters are not version-pinned in the CI container, as pinning would drive either frequent maintenance with upgrades or stagnation of the code-base against older versions.
The combination may result in inconsistent formatting opinions across CI worker nodes[^1].
If you see such behaviour consider changing the thing to force a container refresh.
[^1]: The collection of container builds across all worker nodes may not hold a consistent set of tool versions despite being built from the same specification: The inconsistencies emerge from the cadence of upstream tool package updates beating against the cadence of container rebuilds on the worker nodes.