-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Mac and Windows builds failed for 62 #3174
Comments
It's definitely support for unix sockets in |
Beautiful, thanks for looking into it.
No problem at all: I'll do a pass through the tower-abci repo and see if I can't get it cross-platform-compatible again. |
Missing Windows support for the moment is not a big deal, I don't think it's worth doing extra release shenanigans. We could pick it back up later as changes propagate from upstream. |
Filed a quick |
We'll pick this up in the next release of tower-abci, as we integrate |
There's in-flight work around version upgrades, and given that we've got an extra week for 63 (#3182 (comment)), we may be able to land the necessary version bumps to unbreak the builds. cc @erwanor in case I'm making assumptions. |
Actually this landed with #3192, so we can close this! |
Describe the bug
The
cargo-dist
workflow for building binaries for Linux, Mac, and Windows failed on Testnet 62: https://github.com/penumbra-zone/penumbra/actions/runs/6474718975/job/17580377131 Why?I suspect it could be related to the
tower-abci
v0.10.0 change, which added support for Unix domain sockets for binding pd, and could have thereby broken non-Linux builds. That make sense for the Windows failure, but the Mac build we'd've seen elsewhere.I'll take a stab at building manually on Windows, and see if we need
cfg
attributes in tower-abci. It's also worth asking: do we even want mac & windows binaries prebuilt? I think it's worth a timeboxed attempt to restore functionality, but if it gets complicated, I'll fall back to shipping Linux bins only in the interim.Additional context
First recorded in #3123 (comment)
The text was updated successfully, but these errors were encountered: