| 19 Mar 2022 |
 hexa |
fatal: couldn't find remote ref pull/164601/head
o_O
| 14:09:02 |
 cole-h | Oh boy... | 17:45:39 |
| cole-h | Ah, found the real issue:
This SHA and context has reached the maximum number of statuses. | 17:50:38 |
| hexa | what does that even mean | 17:52:12 |
| cole-h | It likely means, when GitHub was having their bad day, that the API was doing weird things and caused ofborg to continuously attempt to add statuses or something | 17:53:14 |
| cole-h | https://api.github.com/repos/NixOS/nixpkgs/statuses/4e07eedf4dc9dbba87d3591271d158ceb9341f03?per_page=100 | 17:56:15 |
| cole-h | : ~ ; curl -v "https://api.github.com/repos/NixOS/nixpkgs/statuses/4e07eedf4dc9dbba87d3591271d158ceb9341f03?per_page=1" 2>&1 | rg -i 'link:'
< link: <https://api.github.com/repositories/4542716/statuses/4e07eedf4dc9dbba87d3591271d158ceb9341f03?per_page=1&page=2>; rel="next", <https://api.github.com/repositories/4542716/statuses/4e07eedf4dc9dbba87d3591271d158ceb9341f03?per_page=1&page=1167>; rel="last"
| 17:57:23 |
| cole-h | So that commit has ~1167 statuses on it lol | 17:57:36 |
| cole-h | This same thing happened in the past, and I sent in a support ticket and got the above hint to look for how it's exceeding the maximum number of statuses (1000) | 17:59:31 |
| cole-h | hexa: Fetching from the pull head ref should work now :) | 18:00:57 |
| hexa | ❤️ | 18:03:45 |
| 23 Mar 2022 |
 Sandro 🐧 | In reply to @7c6f434c:nitro.chat
Graham has said many times (and correctly), that even a relatively low rate of false-positive-red will devalue red for very clear failures. Build test failures… vary in their expected impact on decisions and how often to we muss grey checks by accident and break things? | 10:56:12 |
