-
Notifications
You must be signed in to change notification settings - Fork 7
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
HTTP 500 #941
Comments
Same here, my Travis CI build failes due to coveralls returning an 500 status code (see https://travis-ci.org/dominique-mueller/angular-notifier/builds/213470146#L705). |
Seems that Coveralls is working again ... |
I am seeing a lot of 500s from the web app, though they seem to be clearing up now. Last night jobs started showing "No data available in table" on the breakdowns, which they are still doing. Is this related? Should I re-submit them? |
I think I know what has been happening with the "No data available in table" -- because I have been trying to debug the coverage reports I have been cancelling all of the other travis jobs that do not contribute to the coveralls report (i.e., all but one), so Travis reports the job as cancelled and coveralls doesn't associates any coverage data with the job -- but it does with the only sub-job that generates any coverage data. All very confusing when combined with the other things that were failing (of which coveralls was only responsible for the brief spate of 500s). |
We are seeing HTTP 500s from the Web UI intermittently. |
I am no longer seeing the 500s on the site itself, but all coverage pushes from CI builds are now throwing 500s. We've had to disable the coveralls push so that our builds continue passing. |
We're getting a lot of 500's when Circle CI tries to upload our coverage. |
https://coveralls.io/repos/ is giving me 500s consistently for the last couple hours. Seems like it may have been triggered by / related to this TravisCI job attempting to report coverage stats, and getting an error back (all 6 builds in the job have this error):
|
Just had a HTTP 500 again in logs of one of the travis builds (svgo prefixIds plugin): [...]
<title>Coveralls :: Oops, something went wrong (500)</title>
[...] |
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions. |
Suddenly some builds of a svgo PR in Travis fail with coveralls service responding with HTTP 500:
https://travis-ci.org/svg/svgo/jobs/213448873#L1166
The text was updated successfully, but these errors were encountered: