Once you have finished, confirm that `gcc` and `make` are installed:
```shell
gcc --version
make --version
$ gcc --version
$ make --version
```
#### CMake
...
...
@@ -96,7 +96,7 @@ The algorithm library of Milvus, Knowhere is written in c++. CMake is required i
Confirm that cmake is available:
```shell
cmake --version
$ cmake --version
```
#### Go
...
...
@@ -106,7 +106,7 @@ Milvus is written in [Go](http://golang.org/). If you don't have a Go developmen
Confirm that your `GOPATH` and `GOBIN` environment variables are correctly set as detailed in [How to Write Go Code](https://golang.org/doc/code.html) before proceeding.
```shell
go version
$ go version
```
#### Docker & Docker Compose
...
...
@@ -121,7 +121,7 @@ Milvus depends on Etcd, Pulsar and minIO. Using Docker Compose to manage these i
To build the Milvus project, run the following command:
```shell
make all
$ make all
```
If this command succeed, you will now have an executable at `bin/milvus` off of your Milvus project directory.
...
...
@@ -135,7 +135,7 @@ Presubmission verification provides a battery of checks and tests to give your p
To run all presubmission verification tests, use this command:
```shell
make verifiers
$ make verifiers
```
### Unit Tests
...
...
@@ -143,12 +143,12 @@ make verifiers
Pull requests need to pass all unit tests. To run every unit test, use this command:
```shell
make unittest
$ make unittest
```
To run single test case, for instance, run TestSearchTask in /internal/proxy directory, use
```shell
go test-v ./internal/proxy/ -test.run TestSearchTask
$ go test-v ./internal/proxy/ -test.run TestSearchTask
```
...
...
@@ -157,23 +157,22 @@ go test -v ./internal/proxy/ -test.run TestSearchTask
Milvus uses Python SDK to write test cases to verify the correctness of Milvus functions. Before run E2E tests, you need a running Milvus: