You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure why the build failed, but i have forked and tested building from main on my own and it seems to be fine. I hypothesize that it might have been due to the instability of github itself but the run is too old to make a determination (no logs retained).
We're pulling the binary from tagged releases in order to deploy to our environment. I'm thinking that we're getting bitten by the bug that was fixed in #211 but there hasn't been a release tagged in a while.
Could someone with the power to do so either try re-running the latest tagged release job or trigger a new one so that updated binaries can be pulled from github?
I'm not sure why the build failed, but i have forked and tested building from main on my own and it seems to be fine. I hypothesize that it might have been due to the instability of github itself but the run is too old to make a determination (no logs retained).
We're pulling the binary from tagged releases in order to deploy to our environment. I'm thinking that we're getting bitten by the bug that was fixed in #211 but there hasn't been a release tagged in a while.
Could someone with the power to do so either try re-running the latest tagged release job or trigger a new one so that updated binaries can be pulled from github?
Let me know if there's anything I can do to help.
Link to failed job: https://github.com/czerwonk/junos_exporter/actions/runs/4144538422
The text was updated successfully, but these errors were encountered: