- Oct 14, 2020
-
-
Georges Racinet authored
-
- Jun 16, 2020
-
-
Georges Racinet authored
Up to now, we didn't declare any requirement in setup.py. We're adopting here a three-layered structure, with the full blown `dev-requirements.txt` carrying the needed tools to recompile the gRPC stubs. grpcio and grpcio-tools can be heavy to install, especially in CI context. We still have the problem that heptapod will pull Mercurial, just hoping it wouldn't mask the stable and default Mercurial versions.
-
- Jan 09, 2020
-
-
Georges Racinet authored
We use the `pytest-grpc` helpers. This implements only the `FindCommit` RPC call, but in a complete manner. This raises several questions: - for now, we have a single `servicer` module, but Gitaly has many services: How shall we organize our code? - the fixtures for gRPC server have the module scope. Shall we have such a fixture for each service? - will we be able to create commits directly with the Gitaly API in the future? - do we want to separate the tests in several layers, ie those that don't need a gRPC server (unit-testing the `changectx_to` functions) and those that do?
-
Georges Racinet authored
We're running tests against latest released Mercurial versions and the heads of the stable and default branches.
-