github-action
github-action copied to clipboard
Fails inconsistently
This plugin succeeds or fails seemingly at random with very little output to follow up on. Below is common output:
with:
github-token: ***
path-to-lcov: ./coverage/lcov.info
coveralls-endpoint: https://coveralls.io
Using lcov file: ./coverage/lcov.info
##[error]Bad response: 500 {"message":"Build processing error.","error":true,"url":""}
##[error]Node run failed with exit code 1
The same check ran from TravisCI and had no problem completing. This seems like a back end issue. Can you make this action more resilient and less error-prone or more verbose so you can debug it?
Here's a link to a random failure and here's a PR made at roughly the same time that passed.
Just as a user like you, I believe this was caused by intermittent failures on their backend and it's unrelated to the action.
That sounds reasonable, but the problem is Travis, CircleCI, etc. seem to never fail though. So what's different/special about those compared to this action?
Timing or something. Does the issue still happen consistently now?
I recall I also had a few failures a couple of days ago and they were fixed after a while
On Tue, Oct 1, 2019, 18:17 Phred Lane [email protected] wrote:
That sounds reasonable, but the problem is Travis, CircleCI, etc. seem to never fail though. So what's different/special about those?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/coverallsapp/github-action/issues/9?email_source=notifications&email_token=AACVLNKAQNYLQN42KOKIJWLQMNS2NA5CNFSM4I3S5IYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEABUTAQ#issuecomment-537086338, or mute the thread https://github.com/notifications/unsubscribe-auth/AACVLNP3KXQWJZJIXMXEBODQMNS2NANCNFSM4I3S5IYA .
Timing or something. Does the issue still happen consistently now? I recall I also had a few failures a couple of days ago and they were fixed after a while
If Travis/Circle or any other method failed at the same time, this would seem logical to me. However this action fails even when other methods do not.
@nickmerwin You have any idea what the problem may be here?