CI: Use -O3 builds for Liquid integration tests.
What the developer wrote
Authored by Rusty Russell
CI: Use -O3 builds for Liquid integration tests.
The other integration tests are taking under an hour, and this is
taking 1hr 30m.
The downside is that backtraces are far less clear, but that's why the
main run uses the full debug version.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
What changed, and why it matters
This commit changes one line in the project's automated testing configuration. It switches the Liquid integration tests to use a faster compiler optimization setting (-O3) so the tests finish sooner. It does not change any code that runs in production, does not fix a bug, and has no security relevance.
No action required. This is a benign CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .github/workflows/ci.yaml, changing the CFG value for the ‘liquid’ CI job from ‘compile-gcc’ to ‘compile-gcc-O3’. This is purely a continuous-integration performance tuning change to reduce test runtime. The commit message explicitly notes the trade-off: backtraces will be less clear, but the main debug run remains unchanged.
Changed components
.github/workflows/ci.yamlInspect captured patch +1 / −1
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index b3892b11..72a9fdee 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -505,7 +505,7 @@ jobs:
# And don't forget about elements (like cdecker did when
# reworking the CI...)
- NAME: liquid
- CFG: compile-gcc
+ CFG: compile-gcc-O3
COMPILER: gcc
TEST_NETWORK: liquid-regtest
TEST_DB_PROVIDER: sqlite3
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.