fix: Don't use perf
in plonk-artifacts workflow
#197
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.
Since the setup action will set both
SP1_DEV=true
andFRI_QUERIES=1
, the plonk artifact generation fails. We can overrideSP1_DEV
but cannot overrideFRI_QUERIES
since different StarkMachines use different values (and they are all overridden by the sameFRI_QUERIES
envvar). Unsetting variables set viaGITHUB_ENV
is not currently supported according to actions/runner#1126So just pass
perf: false
instead. TheMakefile
uses--release
and sets-Ctarget-cpu=native
by itself so we don't need any of theperf
setup items