Workflow badges not updating?

[IndrajeetPatil]

I am not sure if it's a bug with GitHub or there is something amiss with bayestestR, but the badges are not updating to show the current status of the workflows. E.g. all workflows are passing right now, and yet the badges still show that they are failing. That shouldn't happen.

E.g. https://github.com/easystats/bayestestR/workflows/R-CMD-check-strict/badge.svg

[strengejacke]

I guess this just takes some time?

[IndrajeetPatil]

It's still failing. I am pretty sure something is off here. @etiennebacher Do you have any hunches?

[etiennebacher]

Some people had the same issues and apparently fixed it by deleting the previous runs that failed (maybe github actions cache is not updated?)

https://github.com/actions/runner/issues/1830

[IndrajeetPatil]

Thanks, @etiennebacher.

I have deleted caches and have retriggered the workflows. Let's see if the badges update now. 🤞

[IndrajeetPatil]

Hmm, still not working. So strange. We are not doing anything special for bayestestR, so why would they not be working only for this repo?!

[IndrajeetPatil]

Actually, that's not true. Even the easystats meta-package badges are also not up-to-date 👀

https://easystats.github.io/dashboard/dashboard.html#workflow-status

E.g. this should be green ATM: https://github.com/easystats/easystats/workflows/check-random-test-order/badge.svg

[etiennebacher]

I suspect it's something internal to github actions, they had some issues recently (not related to badges, but there could be some caching issues on their side): https://www.githubstatus.com/history

[rempsyc]

I recently experienced the same thing on my new package pubmedDashboard and the trick was to change the URL of the badge by going to the workflow and manually creating a new badge URL for the R CMD check workflow. I can share the exact link later if that would be useful. But that would require changing the README of all easystats packages…

[mahula]

Hello @IndrajeetPatil, when you visit the R-CMD-check-strict worlflow page in your repository and choose the Create status badge menu, you can just copy the correct link for the badge, which works fine and show, that the last R-CMD-check-strict run was successful.