Hello! It seems that markdown implementation caches the images which means that if the build failed during the generation of markdown preview in the package control, the build status badge will always stay red even though the new build is passing (and the actual image under the link is a green one). For an example see https://packagecontrol.io/packages/EasyClangComplete (as of now)
Note that when clicking on a failing build badge you see that it is actually passing.
Why not pointing it to the original location? This is annoying because it creates the illusion that the plugin fails the tests even though it doesn't. This hinders new installations.
Hello! It seems that markdown implementation caches the images which means that if the build failed during the generation of markdown preview in the package control, the build status badge will always stay red even though the new build is passing (and the actual image under the link is a green one). For an example see https://packagecontrol.io/packages/EasyClangComplete (as of now)
Note that when clicking on a failing build badge you see that it is actually passing.
This is the how it looks in package control.
The link to the image is a link to a cached version here: https://packagecontrol.io/readmes/img/1deb0a0e609f82da92819e8fb1f149f885fb50f5.svg which is indeed a red one.
While the original link points to a passing image. This link is just a mangled link to an svg for the master branch: https://travis-ci.org/niosus/EasyClangComplete.svg?branch=master
Why not pointing it to the original location? This is annoying because it creates the illusion that the plugin fails the tests even though it doesn't. This hinders new installations.