Fix CI caching/upload with STATIC_DEPS #374
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CI does not appear to work as intended - for example, none of the CI cases currently appear to respect the "STATIC_DEPS" setting, (e.g. not that no wheel is uploaded where
STATIC_DEPS
is intended to be true: e.g. https://github.com/lxml/lxml/actions/runs/5287691371/jobs/9568495615Github Actions doesn't allow matrix values to be structured objects (I believe they are always strings, even if they look like numbers or booleans) and doesn't seem to automatically update the variable environment from matrix.env.VARNAME.Instead I changed the variables to use the naming conventionenv-VARNAME
and merged them into the job-level variable environment. This makes the CI work as seemingly intended.I considered using a structured value with thetoJSON
/fromJSON
functions but this is less easy to understand and more error-prone.The comparison in the if-statement
matrix.os.STATIC_DEPS == 'true'
is false when given the boolean valuetrue
.It's not clear to me whether
matrix.env
can indeed be anobject
or only astring
. As documented, only strings are allowed, but I filed an issue requesting clarification.