Travis CI invalid badges (rate limiting?)

[jakirkham]

It appears that the repo joyent/node on GitHub was moved and renamed. However, Travis CI does not know this. So, changing the URLs for these badges is needed to fix the examples.

[jakirkham]

Also, seeing this for HHVM badges and MyGet.

[elboletaire]

Not just the examples. Mine were failing so far but whilst I write this post they appear to be ok.

Maybe is something with the cache of shields. If there are projects with a lot of movement and they're building very consecutively maybe shields shows us every time a cached image of an on-going build.

[elboletaire]

Maybe is something with the cache of shields. If there are projects with a lot of movement and they're building very consecutively maybe shields shows us every time a cached image of an on-going build.

Forget that. I've just seen how it changed from passing to unaccessible to passing again and I'm not currently running any build.

[antonmedv]

Same for me!

[Mithgol]

+1

[kgryte]

I am frequently getting inaccessible travis-ci badges. If I refresh my browser two or three times, the badge changes to success. If I leave and come back, the badge says inaccessible again. This is in contrast to the badge directly provided by travis-ci which always shows success.

[espadrine]

I have added a log in prod to identify what causes that. The "normal" cause is that travis does not have that repo registered, which does not seem to be the case here. So far no luck.

[kgryte]

The problem seemed to start, at least for me, within the past week. For an example repo, see here. If you keep refreshing, the travis-ci badge will randomly alternate between inaccessible and success.

[espadrine]

Here is what I have: sometimes, Travis CI returns {"file":"not found"}, sometimes, Retry later, when downloading their badge. Is that a rate-limiting thing?

[espadrine]

Historically, we request badges instead of using the API because the straightforward API queries sometimes produce "pending", which is not a badge people ever want to see, and some other way to use the API to circumvent that had issues when dealing with branches. People wanted our badges to show the same information as the Travis CI badges (with the customizability that we offer).

• Original switch from PNG header sniffing to straightforward Travis API: https://github.com/badges/shields/commit/ee4c9f885a07147b4b5e45b091f137fe3110af9d
• Switch to builds.json to avoid "pending": https://github.com/badges/shields/commit/5050698c14f4530a559ad93ed769c25ae15571e1
• Issues with that, and switch to SVG scraping: https://github.com/badges/shields/issues/288

I have gone full circle, and switched it to only perform a HEAD request, on the SVG headers this time. Let me know if it changes anything.

[bcomnes]

Seeing a lot of invalid travis badges this morning.

[TomasVotruba]

Same here:

• Shields invalid: https://img.shields.io/travis/Zenify/ModularPresenterMapping.svg
• Travis valid: https://travis-ci.org/Zenify/ModularPresenterMapping.svg?branch=master

[ankitpokhrel]

Same problem here!

[Mithgol]

It seems to me that the problem's gone. Is it a weekend's effect, I wonder.

[JayBizzle]

Still seeing the Invalid Travis badges

[netvl]

Indeed, I have the same problem. Shields.io: (https://img.shields.io/travis/netvl/xml-rs.svg?style=flat-square) Travis: (https://travis-ci.org/netvl/xml-rs.svg?branch=master)

Occasionally the shields badge becomes green but usually it is invalid.

[elboletaire]

I currently see them better than before the change. It's true that now they appear as "invalid" sometimes but it's less often than when they said "inaccessible".

[brianreavis]

Also getting a bunch of Invalid badges across many repos.

[artem-malko]

+1

[paulmelnikow]

If this problem recurs, feel free to open a new issue.