-
Notifications
You must be signed in to change notification settings - Fork 169
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
Build failure #192
Comments
Let me take a look this afternoon!
…On Fri, Jan 20, 2023 at 9:28 PM NickCH-K ***@***.***> wrote:
@khwilson <https://github.com/khwilson> I keep getting failed build
warnings on all the new security updates, and so haven't been merging them.
Is there a place I can look to figure out what's going on? I'm not quite
able to figure it out from the logs.
—
Reply to this email directly, view it on GitHub
<#192>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALU5ESR35HWNBXUTG7SHVLWTNCWRANCNFSM6AAAAAAUCEKTHQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@khwilson It appears to be something to do with version 2.6 of Ruby not being available |
@khwilson any ideas here, or something I could fix on my end? At the moment we can't take any PRs until this is fixed @grantmcdermott I don't suppose you know how to fix this |
Hi @khwilson just pinging again - not sure if you've gone dark here. I can try to look around for someone else who knows how to handle a Ruby installation if you're not available. |
I think @khwilson is on paternity leave (at the least he's got his hands full), so we may be on our own here. Unfortunately, I don't know a fix off the bat. We had quite a bit of custom custom scaffolding iirc... |
Oh! Well, well-deserved. Unfortunate; I don't think we can take any PRs or change anything until it's fixed, since any updates won't build. |
We have now solved the installation issue, but have a gemfile issue coming right up behind! Here is the error that's popping up on the build job:
I'm guessing we need an updated version of Ruby? |
PRs are back up and running, but the security updates still throw build errors, appears ot be an old-Ruby-version issue. |
@khwilson I keep getting failed build warnings on all the new security updates, and so haven't been merging them. Is there a place I can look to figure out what's going on? I'm not quite able to figure it out from the logs.
The text was updated successfully, but these errors were encountered: