Clean secp256k1 build artifacts before build #1938
Open
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.
Summary
This PR fixes CI build failures by cleaning the
third-party/secp256k1directory before starting the build process.secp256k1submodulegit clean -fdxandgit checkout .to ensure a clean build stateProblem
The CI build occasionally fails due to stale autotools-generated files in the
secp256k1submodule that conflict with fresh builds.Solution
Added a new step "Clean third-party build artifacts" that runs before the build step to:
third-party/secp256k1git clean -fdxgit checkout .