Cirrus-ci-docs: Task specific badges show a passing build although it failed
Expected Behavior
The tasks should display the actual build status.
Real Behavior
For failing Windows build I have a passing badge displayed in this README.md.
Related Info
This error seems to be different than #294 because the build in question was never successful, so this shouldn't be a cached result.
robertguetzkow
All 22 comments
Definitely something going on with badges that needs to be looked into.
RDIL
on 23 May 2019
@robertguetzkow thank you for reporting! There is indeed a bug in badge calculation for a task in this case. I've identified the issue, already fixed it and it will be deployed shortly.
fkorotkov
on 23 May 2019
@robertguetzkow have you just delete the repository? The fix is deployed but I cannot verify it on your repo (new tests are passing though).
fkorotkov
on 23 May 2019
@fkorotkov Yes, sorry I've deleted the test repository. The link is now fixed and points to the actual repository.
robertguetzkow
on 23 May 2019
Could it be that the fix broke something? ATM it doesn't find the build badges "CI not+found".
robertguetzkow
on 23 May 2019
@robertguetzkow which one? where?
fkorotkov
on 23 May 2019
robertguetzkow
on 23 May 2019
Works for me. 😲
fkorotkov
on 23 May 2019
thats ironic, it says macos is failing yet that screenshot was taken on a mac 😆
RDIL
on 23 May 2019
What your screenshot shows is correct. This is what I see (in an incognito window to avoid caching issues):
What I've seen a few minutes before:
macOS should be failing and BSD should be passing.
robertguetzkow
on 23 May 2019
petition to redo the badge system
press thumbs up to sign
RDIL
on 23 May 2019
I see the same in an incognito windows. 🤔 Will investigate further
fkorotkov
on 23 May 2019
@robertguetzkow since I can't reproduce. Could you please check the readme again to see if anything changes? I've made some queries more consistent.
fkorotkov
on 23 May 2019
It's currently showing "Ci not+found" for all entries. I've also tested this from a remote machine with the same result.
robertguetzkow
on 23 May 2019
I've also tried website like https://www.url2png.com/ but see an expected result:
fkorotkov
on 23 May 2019
🤷♀️ Not sure what is causing this. Do you use some form of CDN that might give different results depending on geographic location? Both computer I tested this on are in Germany.
robertguetzkow
on 23 May 2019
I've tested this over a proxy (US) and got the same result as in the first screenshot with macOS passing and BSD not found. With another proxy (Germany) the result is correct. Another one has all set to "not found" as well. Seems like either one of these three states is occurring. Apparently this behavior is not linked to the physical location of the computer.
Edit: Tested with both Chrome and Firefox.
robertguetzkow
on 23 May 2019
VPN to Australia has same results as mac screenshot
RDIL
on 23 May 2019
Very weird. I'm currently rewriting badge serving for #294. Let's see if it will help. There is no CDN for badges except GitHub's internal caching of pre-rendered Markdown. I also don't see any internal exceptions for your repository. 😪
fkorotkov
on 23 May 2019
Looks like this issue is happening at GitHub, because if I copy & paste the URL (instead of visiting the page where it loads them through camo.githubusercontent.com) everything is displayed correctly.
robertguetzkow
on 23 May 2019
Seems like #294 then. I wonder why it started happening all of the sudden when the badge delivering mechanism was there from day 0 for almost two years. 😢
fkorotkov
on 23 May 2019
Thank you for your help and good luck with the patch for #294 !
robertguetzkow
on 23 May 2019
Related issues
dotdoom
·
5Comments
fkorotkov
·
5Comments
iskakaushik
·
5Comments
cevich
·
5Comments
dotdoom
·
4Comments
Most helpful comment
petition to redo the badge system
press thumbs up to sign