search

lemurheavy / coveralls-public

The public issue tracker for coveralls.io
http://coveralls.io
124 stars 7 forks source link

Github-status with `flag_name` not being reported to github repositories #1734

Open joostleuven opened 8 months ago

joostleuven commented 8 months ago

Since last Friday (Nov 3 2023) the github-statuses using the flag_name option are no longer reporting on our github.com repos. This seems to have happened for all our repos at the same time. We do still receive the coverage/coveralls (push) github status.

joostleuven commented 8 months ago

It seems to have happened between: 02 Nov 2023 10:42PM CEST and 03 Nov 2023 09:07AM CEST. I saw a mention of a deploy on this issue: https://github.com/lemurheavy/coveralls-public/issues/1733. Could that be related to it somehow?

Is there something that we need to change in the parameters that are being sent to coveralls? We're on the latest version of the coveralls-integration

afinetooth commented 8 months ago

Hi, @joostleuven.

Can you please confirm your repo (and one or more builds with a failing flag_name status) for me?

I'll see if I can figure it out in the meantime.

Thanks.

afinetooth commented 8 months ago

@joostleuven, I'm afraid I can't tell which project is giving you the trouble, but that said, you appear to be a member of a paid Coveralls subscription, so you can get priority support by emailing us at support@coveralls.io.

Feel free to do that as the follow-up here if you wish and you can just refer to this issue. Might be useful if the repo in question is private or any info is sensitive. (Not that anyone else can access it if it is, but you might just prefer not sharing its location in a public forum.)

joostleuven commented 8 months ago

Thank you @afinetooth I'll reach out to support. It's indeed a private repository.

afinetooth commented 7 months ago

Hi, @joostleuven. Just wanted to follow up and confirm that a response was sent to you from support@coveralls.io.

I also wanted to confirm, for others who may be affected, that there was an impact on some projects' status updates after that deploy on Nov 2, and we are still closing some related issues. If you feel you may have been affected by that, please let us know at support@coveralls.io, regardless of whether you are a paid or open source user.