-
Notifications
You must be signed in to change notification settings - Fork 18
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: This now fails where previously it was working. #16
Comments
file that triggers the above: https://github.com/provenance-io/explorer-service/blob/main/.github/workflows/build.yml |
I have experienced the same issue and i can't for the life of me figure out what is specifically causing this as we are having all CI builds fail currently. Seems to error internally without throwing any logs or other key information. @gando001 Seems to be an issue introduced with v.0.3.1 released three hours ago. @crussell-figure as an FYI we have specifically required v.0.3.0 and this has fixed the issue for the time being. Remember to check when it's fixed and this can be reverted to the "@master" selection |
Same issue here. I forked the repo as a temporary measure. An upstream urgent fix would be hugely appreciated. |
Upstream's latest changes are causing mayhem in the build pipelines. This change reverts upstream's latest commit. Upstream issue: rokroskar/workflow-run-cleanup-action#16
Hey all! @rokroskar: I've created two PRs which fix this issue(#17 / #18). I wasn't sure which way you like more. Personally I prefer #17. |
I hope it will be solved soon, currently our CI is also blocked by this |
Sorry for the inconvenience. I am expecting this to be fixed today. |
Apologies for the delay with fixing it in master - in the meantime pin to |
And apologies @rokroskar for your inconvenience.. I've caused this by accident. Hopefully this won't ruin our collab in the future ^^ |
Thanks @mustaphazorgati no need to apologize for introducing a bug! I should have tested the PR a bit more carefully (speaking of which, if someone wants to write tests for this action that would be great (see #19)!) In any case, the fix is now merged and |
Thank you for addressing this. |
You're welcome @crussell-figure. |
Upstream's latest changes are causing mayhem in the build pipelines. This change reverts upstream's latest commit. Upstream issue: rokroskar/workflow-run-cleanup-action#16
Upstream's latest changes are causing mayhem in the build pipelines. This change reverts upstream's latest commit. Upstream issue: rokroskar/workflow-run-cleanup-action#16
Upstream's latest changes are causing mayhem in the build pipelines. This change reverts upstream's latest commit. Upstream issue: rokroskar/workflow-run-cleanup-action#16
I don't know exactly why this action is failing now, but previously it was working fine.
Previously:
The text was updated successfully, but these errors were encountered: