Repository navigation
Conversation
|
❌ Build pvxs 1.0.910 failed (commit 9bb3f3b8bd by @jacomago) |
|
Investigating This action pulls in On Debian derivatives, the equivalent is done by From some searching, I'm unsure how wrt. |
|
wrt. this PR. I'm impressed that a build takes only 40 minutes. Most of this being to compile epicscorelibs, which happens less frequently. I'm already accustomed to long CI runs for epics-base, so I think these times are acceptable to me. To move forward, equivalent PRs for epicscorelibs and P4P are needed. I will be interested to see what happens with the P4P unit tests. The last time I tried, I found that qemu-user didn't implement some ~obscure |
|
I was able to persuade Indeed IP_MULTICAST_ALL, SO_RXQ_OVFL, IP_MULTICAST_IF, and IPV6_MULTICAST_IF are not translated as of qemu/qemu@b455ce4. PVXS doesn't treat any of these as fatal errors. |
|
I will work on epicscorelib, I guess that should make pvxs build faster as well. Alternative to using qemu is to use a third party runner from https://buildjet.com/for-github-actions or https://actuated.dev/ which I guess would fix the p4p test failures. Mostly it would be nice if actions/runner-images#5631 could be closed... |
|
Closing in favour of https://github.blog/changelog/2023-10-30-accelerate-your-ci-cd-with-arm-based-hosted-runners-in-github-actions/ in the future. |
|
Picking this up on native ARM runners rather than QEMU. Opened as three PRs, to be merged in dependency order: epics-base/epicscorelibs#56, #201, epics-base/p4p#226. |
Also remove osx 2.7 intel as it is no longer supported by github.