Patrick Steinhardt <ps@xxxxxx> writes: > I think it depends. If we use the REFFILES prereq for the files-specific > tests, then we should likely also use the REFTABLE prereq for the > reftable-specific tests. Correct. I've assumed that as a given; while introducing any new implementation of a subsystem that has widespread impact, we would test things with the original and new implementations. It happened while we were moving "ort" to replace "recursive" as an internal tree merge machinery, for example. linux-TEST-vars job that is available both in GitHub and GitLab CI is an example of a separate job that runs everything with non-default configurations, and "use reftable as the default backend" GIT_TEST_REFTABLE knob may be an appropriate thing to set there. > But that raises the question of whether we want to add a CI job that > exercises code with the reftable backend for every major platform > (Linux, macOS, Windows). If so then your proposal would be fine with me > as we make sure that things work alright on all of them. But if we think > that this would be too expensive then I'd like to at least have very > basic test coverage on all platforms by always running these > backend-specific tests. > > Patrick
