Jeff King <peff@xxxxxxxx> writes: > Yeah, I know. My main beef was that because it fails CI, the urgency of > doing that fix gets pushed onto people working on their individual > topics (in fact there is nothing for you to fix yet because I haven't > even sent these topics upstream). I don't know how to solve that without > stopping its use in the vsbuild CI job, though. What I am not getting is in what way it blocks you (or others who do not deeply care about Windows) to leave vsbuild CI job broken. Do you have some automation that is gated by all the CI jobs to pass, or do you just dislike failing CI jobs out of principle? I pretty much got used to seeing occasional failures and learned to ignore it (e.g. https://travis-ci.org/github/git/git/jobs/716661598 that ends with Makefile:2467: *** unterminated variable reference. Stop. make: *** Waiting for unfinished jobs.... ).
