Wrong badge status reported on GitHub project

[rstoenescu]

The status badge for my project is wrong. It says “failed” which is wrong. It should say “success”. Please take a look below and check out the links which prove my point.

Github project page: https://github.com/rstoenescu/gulp-pipes
CircleCI project page: https://circleci.com/gh/rstoenescu/gulp-pipes

[kimh]

Looks there is a bug on our end. We’ll take a look.

[rstoenescu]

Thanks for the effort!

[fuhrysteve]

I believe the issue is you need to add the HTTP header Cache-Control: no-cache

Please see this github issue

Thanks!

[qrohlf]

@kimh did you ever get a bugfix out for this? I am seeing similar behavior in my project, seems to be related to this issue and Auto-cancel causes status badge to show failure

[eddiewebb]

I’m seeing this behavior still, and suspect its linked to cancelled builds.
Github sees passing status on latest commit:

CircleCI HIstory sees passing status (and older cancellation)

But badge insists its failing:

[halfer]

Related:

Badge is green even if some builds in the workflow failed

The CircleCI badge here shows as passing: https://github.com/coq/coq#coq But the most recent commit in the (master) branch was actually failing: https://circleci.com/gh/coq/workflows/coq/tree/master Given that we use the Workflow feature, may it be due to an absence of Workflow support in badges (the workflow as a whole failed because some builds failed, but the last build to finish in the workflow succeed and may have wrongly set the badge to passing).

[smokku]

I hate writing “mee too” posts, but I am observing exactly the same as @eddiewebb
My builds are fine, yet the badge generated by CI is showing red FAILED status.

[eddiewebb]

Super excited to share that this issue has been resolved! For folks experiencing the issue related to old build statuses being reported in projects that switching to/from 2.0 workflows, the proper badge should now be displayed!