Skip to content
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

Closed
strarsis opened this issue Mar 21, 2017 · 10 comments
Closed

HTTP 500 #941

strarsis opened this issue Mar 21, 2017 · 10 comments

Comments

@strarsis
Copy link

strarsis commented Mar 21, 2017

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

@dominique-mueller
Copy link

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).

@dominique-mueller
Copy link

Seems that Coveralls is working again ...

@cdornan
Copy link

cdornan commented Mar 21, 2017

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?

@cdornan
Copy link

cdornan commented Mar 21, 2017

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).

@jacobbaskin
Copy link

We are seeing HTTP 500s from the Web UI intermittently.

@benjamincharity
Copy link

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.

@kristofclaes
Copy link

We're getting a lot of 500's when Circle CI tries to upload our coverage.

@ryan-williams
Copy link

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):

[info] Statement coverage.: 84.19%
[info] Branch coverage....: 79.41%
[info] Coverage reports completed
[info] All done. Coverage was [84.19%]
[success] Total time: 6 s, completed Apr 3, 2017 4:42:28 PM
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[info] Repository = ./.git
[error] Uploading to https://coveralls.io failed: Couldn't find a repository matching this job.
[error] The error message 'Couldn't find a repository matching this job' can mean your repo token is incorrect.

example full log

@strarsis
Copy link
Author

strarsis commented Apr 6, 2017

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>
[...]

@stale
Copy link

stale bot commented Apr 3, 2020

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.

@stale stale bot closed this as completed Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants