| commit | e347f825463040930c159ab48db49f6ac120a8b6 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jul 24 10:00:45 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Oct 20 10:18:17 2025 -0400 |
| tree | 03aba68b7481a7be1d6d928edf5a3a39f453a20f | |
| parent | eae557cf65c82b4647fb7e3af2866b7025559fb0 [diff] |
build-unit-test-docker: use ubuntu-toolchain-r for gcc Ubuntu plucky uses GCC-15.0, which has a few known bugs. Switch to picking up GCC from the ubuntu-toolchain-r repository, which currently has GCC-15.2. One specific issue the community has encountered included with this fixes is reported by Google Test[1]. [1]: https://github.com/google/googletest/issues/4759 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id7f9cfd9c6292334b79c6c417c11210910876f06
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.