Patrick Steinhardt <ps@xxxxxx> writes: > I think it would be a bit sad to disable those jobs. They build and pass > the test suite alright in Git itself, even though they fail downstream > in Git for Windows. They help me quite a bit to ensure that I don't > regress anything that already is working while I'm iterating on the > current set of features. So in the end, I view them more as testing more > variants of Windows than replacing what we currently have, similar to > how we test Git on different Linux distributions. Hmph, but compared to Linux or macOS platforms, do developers on Windows (and users of Git on Windows, including but not limited to users of Git-for-windows) benefit from having the code base to be tested on "more variants of Windows", or would it be more noise that they need to go visit the failing CI and spend time to triage if the breakage is something they should worry about? The above is more or less a rhetorical question. I think by now everybody knows I do not like monoculture, and if we had infinite engineering resources, I would think it would be healthy to have more than one prominent and competing Windows port of Git (no, I know about Cygwin, but I hear that the platform is POSIXy enough, so I do not exactly consider Git running on Cygwin qualifies as "a Windows port"). But we do not seem to live in such a world. > I have said before that I'm very willing to help to figure out any > issues, regardless of which platform, and I stand by that > statement -- if you see anything that is broken in this context > and report the issue to me I'll jump on it immediately. It's ultimately up to Windows folks to take you up on the offer. >> > Nevertheless, there is currently this huge push, including breaking >> > changes after -rc1 and all, for switching to Meson. Therefore, we need >> > to make it work, somehow, even in Git for Windows' SDK, hence this >> > patch, at this point in time. >> ... > That's completely fair. The CI job we have isn't meant to verify that we > have a G4W-compatible distribution falling out of it, it merely verifies > that we can build and pass tests in such a "standalone" (that is, > without the SDK) configuration. We might eventually want to introduce > another job that _does_ use the SDK with Meson, as well, but I didn't > yet see a need for that until now. Knowing that it is the most widely used platform, I naturally and naïvely was expecting and hoping that there are folks other than Dscho who have enough bandwidth and inclination to help in this area, but so far, having a set of jobs in CI that use a toolchain that is different from what G4W uses (as expected) did not quite help X-<. Nobody noticed it until the last minute. Which made me say that we do not seem to live in such a world, which in turn makes me accept that putting all Windows eggs in a single basket and watch it closely may be a reasonable alternative when it comes to Windows [*], than hoping that diverse set of different builds eventually help flourishing Windows developer community. I dunno. [Footnote] * Yes, I admit that it may be another way to say that I do not care the particular platform deeply enough.
