This pull request significantly reduces the cost of Scalar functional tests. It removes all of the tests that are about how Git commands interact in a sparse-checkout environment. Similar tests exist in the upstream Git project and are no longer required to keep microsoft/git clean of defects in this area. Removing these tests will save resources and reduce flakiness in microsoft/git pull requests.
The functional tests that remain are related to Scalar config, shared object caches, and the GVFS Protocol running against a real Azure DevOps server.
In a second commit, this also removes the functional tests from the CI builds, since they are currently broken. The break is due to the pinned Git version which has not been updated in a while. The correctness of the functional tests is done by running tests from microsoft/git.
This pull request significantly reduces the cost of Scalar functional tests. It removes all of the tests that are about how Git commands interact in a sparse-checkout environment. Similar tests exist in the upstream Git project and are no longer required to keep
microsoft/git
clean of defects in this area. Removing these tests will save resources and reduce flakiness inmicrosoft/git
pull requests.The functional tests that remain are related to Scalar config, shared object caches, and the GVFS Protocol running against a real Azure DevOps server.
In a second commit, this also removes the functional tests from the CI builds, since they are currently broken. The break is due to the pinned Git version which has not been updated in a while. The correctness of the functional tests is done by running tests from
microsoft/git
.