-
Notifications
You must be signed in to change notification settings - Fork 3
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
[BUG] magellan build fails in bmclib
dependency
#45
Comments
Does building with |
Our latest release uses go 1.21 and goreleaser 2.1.0 through our github build automation. Have you tried that configuration? Release: https://github.com/OpenCHAMI/magellan/releases/tag/v0.0.18 |
Ah, yes I forgot to mention that the above snippet came from running Building with
|
Thanks - I will try that. |
Strange. I'm not getting that on my working tree, but I did run into the issue when cloning the repo and trying to build with |
I rebuilt with |
I don't have a linux vm available to test with. Can you use the binary from the release in the meantime? |
Gah!
This is not a magellan problem, I'll try to find another environment with newer |
Can we close this issue? |
Maybe you can tell me.
However,
|
Looks like the |
@bcfriesen Can you try building with the |
Thanks!
|
Looks pretty straight-forward to fix. I guess I can't ignore checking those |
FYI, this is fixed on the |
Yes! It works now.
but those look like spurious(?) failures since I am doing this from a laptop with no access to a BMC. Thanks very much for your help! |
You're welcome! I guess I'll need to take that into account for the other PR I'm working on regarding the tests. They're not complete yet, so I'd pretty much expect them to fail under most circumstances. |
Greetings,
while trying to build magellan for the first time on an x86 VM, I find that the build fails here:
This uses commit
10eabf2
of megellan, Go version 1.22.5, andgoreleaser
version 1.18.2.The text was updated successfully, but these errors were encountered: