Johannes Schindelin wrote: > On Thu, 10 Jun 2021, Luke Shumaker wrote: > > > On Thu, 10 Jun 2021 03:13:29 -0600, > > Johannes Schindelin via GitGitGadget wrote: > > > This particular condition, however, was never tested on Windows, > > > > I was going to say that I do have CI set up[0] to run the subtree > > tests on Windows, and was going to ask for assistance in figuring out > > how to set up CI's Windows to match the behavior that you're seeing > > with Cygwin. > > > > However, upon closer inspection: Because of how run-test-slice.sh > > works, it wasn't actually running the subtree test on Windows. Oops. > > Right, I am sorry about that, it did bite me recently, too. > > > Now, that CI setup was just on my personal copies and hadn't been > > submitted upstream, since I wasn't sure if it was welcome[1]. I never > > really got a reply to that part, but but now that we've got buy-in > > from Ævar for running the tests in contrib/,[2] I might spend some > > more time on it and try to get that submitted. > > I am not so sure about running tests in contrib/ as part of the CI. But we already do run contrib tests: t1021-rerere-in-workdir.sh t3000-ls-files-others.sh t9902-completion.sh t9903-bash-prompt.sh > Those bits and pieces are in contrib/ to indicate that they should > _not_ be considered as adding to Junio's maintenance burden, and > adding them to CI would contradict that. People rely on contrib and distributions build packages enabling what is in contrib. Part of a successful release is contrib not being broken, so Junio can't just ignore the status of contrib. I agree this is not goood, but that's the current situation we are in, and that's because we have allowed perfectly widely used and stable software on the same cohort as unmaintained waste nobody cares about. -- Felipe Contreras
