CI: fix env context reference in job-level env sections.
What the developer wrote
Authored by Christian Decker
CI: fix env context reference in job-level env sections.
GitHub Actions doesn't allow referencing workflow-level env variables
from job-level env sections. Fixed by:
- Replacing ${{ env.PYTEST_OPTS_BASE }} with full values in job-level env
- Keeping ${{ env.PYTEST_OPTS_BASE }} in step-level env (which is valid)
This resolves the "Unrecognized named-value: 'env'" errors.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
What changed, and why it matters
This commit fixes a GitHub Actions workflow syntax error. It replaces an invalid reference to a workflow-level environment variable inside job-level environment sections with the actual values. There is no security issue here—it's purely a CI configuration bug fix that stops 'Unrecognized named-value: env' errors.
No security action needed. Treat as a normal CI maintenance fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is confined to .github/workflows/ci.yaml. GitHub Actions does not permit ${{ env.PYTEST_OPTS_BASE }} in job-level env blocks, so the patch inlines the base pytest options wherever they were referenced at the job level and adds the same inline reference to one step-level env block. This is a YAML/workflow correctness fix with no product code or security boundary changes.
Changed components
.github/workflows/ci.yamlInspect captured patch +6 / −5
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index 3bd67893..7ccc7361 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -318,6 +318,7 @@ jobs:
LIGHTNINGD_POSTGRES_NO_VACUUM: 1
VALGRIND: ${{ matrix.VALGRIND }}
PREV_LIGHTNINGD: /tmp/old-cln/usr/bin/lightningd
+ PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }}
run: |
env
cat config.vars
@@ -336,7 +337,7 @@ jobs:
timeout-minutes: 120
env:
RUST_PROFILE: release # Has to match the one in the compile step
- PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }}
+ PYTEST_OPTS: --reruns=10 -vvv --junit-xml=report.xml --timeout=1800 --durations=10
needs:
- compile
strategy:
@@ -452,7 +453,7 @@ jobs:
env:
RUST_PROFILE: release # Has to match the one in the compile step
CFG: compile-gcc
- PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }} --test-group-random-seed=42
+ PYTEST_OPTS: --reruns=10 -vvv --junit-xml=report.xml --timeout=1800 --durations=10 --test-group-random-seed=42
needs:
- compile
strategy:
@@ -530,7 +531,7 @@ jobs:
RUST_PROFILE: release
SLOW_MACHINE: 1
TEST_DEBUG: 1
- PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }} --test-group-random-seed=42
+ PYTEST_OPTS: --reruns=10 -vvv --junit-xml=report.xml --timeout=1800 --durations=10 --test-group-random-seed=42
needs:
- compile
strategy:
@@ -609,7 +610,7 @@ jobs:
env:
VALGRIND: 0
GENERATE_EXAMPLES: 1
- PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }}
+ PYTEST_OPTS: --reruns=10 -vvv --junit-xml=report.xml --timeout=1800 --durations=10
TEST_NETWORK: regtest
needs:
- compile
@@ -655,7 +656,7 @@ jobs:
timeout-minutes: 120
env:
RUST_PROFILE: release # Has to match the one in the compile step
- PYTEST_OPTS: ${{ env.PYTEST_OPTS_BASE }}
+ PYTEST_OPTS: --reruns=10 -vvv --junit-xml=report.xml --timeout=1800 --durations=10
needs:
- compile
strategy:
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.