-
Notifications
You must be signed in to change notification settings - Fork 75
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
action fails with error from getOptions #26
Comments
Any news on this? Still happening to me... |
I'm also running into the same issue. https://github.com/bryceosterhaus/clay/pull/54/checks Any ideas for a work around? |
Hi all, we released a new version (1.1.0) that should fix this issue: https://github.com/marketplace/actions/coveralls-github-action?version=v1.1.0 Can you please upgrade and try another build? |
@nickmerwin still getting the same error with new run: https://github.com/bryceosterhaus/clay/pull/54/checks?check_run_id=635134295#step:9:8 |
Hi @bryceosterhaus it appears this is an issue with GitHub Action's JS: I'm upgrading those packages now and will release a new version shortly. |
Ok, @bryceosterhaus new version is here: https://github.com/coverallsapp/github-action/releases/tag/v1.1.1 Could you upgrade and build again, please? |
@nickmerwin still getting the same/similar error. I also just tried running the action off of master and got the same issue. btw thanks for the quick replies! |
Hi all, we were able to solve this by removing the - name: Checkout BASE
uses: actions/checkout@v2
with:
ref: ${{ github.event.pull_request.head.sha }} bryceosterhaus/clay#55 (review) That caused unintended behavior since the Action for a PR build will automatically use GitHub's ephemeral merge commit, which is what Coveralls is expecting. If anyone has a use case that requires Thanks. |
Trying to resolve coverallsapp/github-action#26 Also a couple other updates.
Still happens for our projects. The workflow file:
This is not consistent - worked just fine fo this sha: 83942e1dfd0afd1003618459d25cd37cb3147124 |
@nickmerwin Please see the comment above. |
Getting the same problem, for example with this PR elm-tooling/elm-language-server#341 |
@razzeee Switching to actions/checkout@v2 with fetch-depth 0 seems to help. |
Thx only switched to v2, but already seems better |
I've seen this happen a handful of times and am not sure how to reproduce. The error output is:
The text was updated successfully, but these errors were encountered: