Conversation
Add a workflow that runs Bitcoin Core CI jobs against libmultiprocess by overlaying the repository into the bitcoin/src/ipc/libmultiprocess subtree during CI.
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process. |
|
Oh I was about to open one too, see #253. |
Thanks! I'm happy to go with your version. It seems like the workflows are just being ignored though? Not sure if you have any ideas to debug |
|
Looks like the CI jobs here also (like in #253) get skipped because they're using caching which needs a whitelist: |
|
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 |
55a9b55 ci: set Bitcoin Core CI test repetition (Sjors Provoost) fb0fc84 ci: add TSan job with instrumented libc++ (Sjors Provoost) 0f29c38 ci: add Bitcoin Core IPC tests (ASan + macOS) (Sjors Provoost) Pull request description: Slightly more elaborate version of #252 with ccache and depends caching. ACKs for top commit: ryanofsky: Light code review ACK 55a9b55. I looked at all the code here and confirmed it should be safe and the build steps make sense. But did not look closely enough to follow all the internal logic and be very sure there aren't bugs. Tree-SHA512: 4ae72a4603241678a3cd4d41e9e68c4587759279f356e7f51a3e368aec800cac2548e4d55cd1e268406ada6e6977d6a8a7b2dcdb52291208444d5e3b70701e64
3 participants
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)