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.

Sign up for GitHub

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

Jump to bottom

BadRequest when trying to upload coverage report #1658

Closed
tpodolak opened this issue Aug 12, 2022 · 2 comments
Closed

BadRequest when trying to upload coverage report #1658

tpodolak opened this issue Aug 12, 2022 · 2 comments

Comments

@tpodolak
Copy link

tpodolak commented Aug 12, 2022 •
edited
Loading

Hi
We've been using coveralls.io for years as part of NSubstitute.Analyzers pipline. Everything has been working great so far, however suddenly our pull requests started failing during coverage report upload, with following response

<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>

We didn't change anything in the coverage report generation or code responsible for upload(we use community created package https://github.com/csmacnz/coveralls.net for coveralls integration), so it is looks like that either there was a change in the API, or our code coverage report became invalid. Here is a payload sent by coveralls.net (captured from local machine, so some Appveyor specific bits might be missing)
coveralls.txt

Do you see any obvious issues with payload or can you point me where to look for an issue?
@afinetooth
Copy link
Collaborator

@tpodolak check out this issue to see if it matches yours:

csMACnz/coveralls.net#110

We've seen it at least 2 other times in the past few weeks.

Let me know if it's something else.

@tpodolak
Copy link
Author

Yes, that was it. Thanks for quick reply

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@afinetooth @tpodolak