Add a workflow that runs Bitcoin Core CI jobs against libmultiprocess by overlaying the repository into the bitcoin/src/ipc/libmultiprocess subtree during CI.
Approach suggested by maflcko #250 (comment)
Add a workflow that runs Bitcoin Core CI jobs against libmultiprocess by overlaying the repository into the bitcoin/src/ipc/libmultiprocess subtree during CI.
Approach suggested by maflcko #250 (comment)
Add a workflow that runs Bitcoin Core CI jobs against libmultiprocess
by overlaying the repository into the bitcoin/src/ipc/libmultiprocess
subtree during CI.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
Looks like the CI jobs here also (like in #253) get skipped because they're using caching which needs a whitelist:
The actions bitcoin/bitcoin/.github/actions/clear-files@master, bitcoin/bitcoin/.github/actions/configure-environment@master, bitcoin/bitcoin/.github/actions/restore-caches@master, bitcoin/bitcoin/.github/actions/configure-docker@master, and bitcoin/bitcoin/.github/actions/save-caches@master are not allowed in bitcoin-core/libmultiprocess because all actions must be from a repository owned by bitcoin-core or match one of the patterns: actions/checkout@*, cachix/install-nix-action@*, vmactions/*.
Thanks! Closing this in favor of #253. For future reference, it seems like you need to go to the https://github.com/bitcoin-core/libmultiprocess/actions page to see the startup errors, and you can't see errors by using the CI links on the PR page