From 8c5d3f83892ce2fdb01525e96c5298668eaf559d Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Sat, 7 Dec 2019 11:52:57 -0700 Subject: [PATCH 1/3] Update Build Guides for VTTOP removal Signed-off-by: Morgan Tocker --- .../en/docs/contributing/build-on-centos.md | 61 +++++------------ .../en/docs/contributing/build-on-macos.md | 66 +++++-------------- .../en/docs/contributing/build-on-ubuntu.md | 48 +++++--------- 3 files changed, 48 insertions(+), 127 deletions(-) diff --git a/content/en/docs/contributing/build-on-centos.md b/content/en/docs/contributing/build-on-centos.md index 3bb33ff48..d4582b4ae 100644 --- a/content/en/docs/contributing/build-on-centos.md +++ b/content/en/docs/contributing/build-on-centos.md @@ -43,8 +43,8 @@ sudo yum install -y make unzip g++ etcd curl git wget **Notes:** -* Vitess currently has some tests written in Python, but this dependency can be avoided by running the tests in Docker (recommended). -* We will be using etcd as the topology service. The `bootstrap.sh` script can also install Zookeeper or Consul for you, which requires additional dependencies. +* We will be using etcd as the topology service. The command `make tools` can also install Zookeeper or Consul for you, which requires additional dependencies. +* Vitess currently has some additional tests written in Python, but we will be skipping this step for simplicity. ### Disable SELinux @@ -54,20 +54,14 @@ SELinux will not allow Vitess to launch MySQL in any data directory by default. sudo setenforce 0 ``` -### Install Docker - -Running the testsuite requires that you [install Docker](https://docs.docker.com/install/). Should you decide to skip this step, you will still be able to compile and run Vitess. - ## Build Vitess -Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo. After doing so, navigate to the `src/vitess.io/vitess` directory. +Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo: ``` -mkdir -p ~/vitess -cd ~/vitess -git clone https://github.com/vitessio/vitess.git \ - src/vitess.io/vitess -cd src/vitess.io/vitess +cd ~ +git clone https://github.com/vitessio/vitess.git +cd vitess ``` Set environment variables that Vitess will require. It is recommended to put these in your `.bashrc`: @@ -80,33 +74,34 @@ export PATH=$PATH:/usr/local/go/bin # Vitess export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` -Run `bootstrap.sh` script to download additional dependencies. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`): +Build Vitess: ``` -BUILD_PYTHON=0 BUILD_JAVA=0 ./bootstrap.sh +make build ``` -Build Vitess: +## Testing your Binaries + +The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: ``` -source ./dev.env -make build +make tools +make test ``` -## Testing your Binaries +## Running the local example -Run the included local example: +In addition to running tests, you can try running the [local example](../../get-started/local): ``` cd examples/local ./101_initial_cluster.sh ``` + You should see the following: ``` $ ./101_initial_cluster.sh @@ -157,16 +152,6 @@ Access vtgate at http://localhost:15001/debug/status You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. -### Full testsuite - -To run the testsuite in Docker: - -``` -make docker_test flavor=mysql57 -``` - -Running the full suite currently takes 2+ hours to complete. - ## Common Build Issues ### Key Already Exists @@ -192,14 +177,6 @@ E1027 18:28:23.464780 19483 mysqld.go:734] mysqld --initialize-insecure failed mysqld: [ERROR] Fatal error in defaults handling. Program aborted! ``` -### Python Errors - -The end-to-end test suite currently requires Python 2.7. We are working on removing this dependency, but in the mean time you can run tests from within Docker. The MySQL 5.7 container provided includes the required dependencies: - -``` -make docker_test flavor=mysql57 -``` - ### No .installed_version file This error indicates that you have not put the required vitess environment variables in your `.bashrc` file: @@ -212,14 +189,12 @@ cat: /dist/etcd/.installed_version: No such file or directory Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` ### Cannot create dir /etcd -This indicates that the environment variable `VTDATAROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: +This indicates that the environment variable `VTROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: ``` ./101_initial_cluster.sh @@ -230,8 +205,6 @@ mkdir: cannot create directory ‘/etcd’: Permission denied Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` diff --git a/content/en/docs/contributing/build-on-macos.md b/content/en/docs/contributing/build-on-macos.md index 75098b579..eac58ea48 100644 --- a/content/en/docs/contributing/build-on-macos.md +++ b/content/en/docs/contributing/build-on-macos.md @@ -36,14 +36,12 @@ Running the testsuite requires that you [install Docker](https://docs.docker.com ## Build Vitess -Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo. After doing so, navigate to the `src/vitess.io/vitess` directory. +Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo: ``` -mkdir -p ~/vitess -cd ~/vitess -git clone https://github.com/vitessio/vitess.git \ - src/vitess.io/vitess -cd src/vitess.io/vitess +cd ~ +git clone https://github.com/vitessio/vitess.git +cd vitess ``` Set environment variables that Vitess will require. It is recommended to put these in your `~/.bash_profile` file: @@ -51,54 +49,36 @@ Set environment variables that Vitess will require. It is recommended to put the ``` # Vitess export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` -Run `bootstrap.sh` script to download additional dependencies. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`): +Build Vitess: ``` -BUILD_PYTHON=0 BUILD_JAVA=0 ./bootstrap.sh -``` - -This should result in output similar to the following: +make build ``` -morgans-mini:vitess morgo$ BUILD_PYTHON=0 BUILD_JAVA=0 ./bootstrap.sh -creating git hooks -installing protoc 3.6.1 ---2019-11-05 14:44:32-- https://github.com/protocolbuffers/protobuf/releases/download/v3.6.1/protoc-3.6.1-osx-x86_64.zip -Resolving github.com (github.com)... 140.82.114.4 -Connecting to github.com (github.com)|140.82.114.4|:443... connected. -HTTP request sent, awaiting response... 302 Found -... -... -... -2019-11-05 14:44:39 (20.1 MB/s) - ‘consul_1.4.0_darwin_amd64.zip’ saved [34526567/34526567] - -Archive: consul_1.4.0_darwin_amd64.zip - inflating: consul -bootstrap finished - run 'source dev.env' or 'source build.env' in your shell before building. -``` +## Testing your Binaries -Build Vitess: +The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: ``` -source ./dev.env -make build +make tools +make test ``` -## Testing your Binaries +## Running the local example -Run the included local example: +In addition to running tests, you can try running the [local example](../../get-started/local): ``` cd examples/local ./101_initial_cluster.sh ``` + You should see the following: + ``` $ ./101_initial_cluster.sh morgans-mini:local morgo$ ./101_initial_cluster.sh @@ -106,8 +86,6 @@ enter etcd2 env add /vitess/global add /vitess/zone1 add zone1 CellInfo -Error: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint -Error: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint etcd start done... enter etcd2 env Starting vtctld... @@ -146,16 +124,6 @@ Access vtgate at http://morgans-mini.lan:15001/debug/status You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. -### Full testsuite - -To run the testsuite in Docker: - -``` -make docker_test flavor=mysql57 -``` - -Running the full suite currently takes 2+ hours to complete. - ## Common Build Issues ### Key Already Exists @@ -186,14 +154,12 @@ cat: /dist/etcd/.installed_version: No such file or directory Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` ### Cannot create dir /etcd -This indicates that the environment variable `VTDATAROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: +This indicates that the environment variable `VTROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: ``` ./101_initial_cluster.sh @@ -204,8 +170,6 @@ mkdir: cannot create directory ‘/etcd’: Permission denied Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` diff --git a/content/en/docs/contributing/build-on-ubuntu.md b/content/en/docs/contributing/build-on-ubuntu.md index 63989cac7..c12267758 100644 --- a/content/en/docs/contributing/build-on-ubuntu.md +++ b/content/en/docs/contributing/build-on-ubuntu.md @@ -51,8 +51,8 @@ sudo systemctl disable etcd **Notes:** -* Vitess currently has some tests written in Python, but this dependency can be avoided by running the tests in Docker (recommended). -* We will be using etcd as the topology service. The `bootstrap.sh` script can also install Zookeeper or Consul for you, which requires additional dependencies. +* We will be using etcd as the topology service. The command `make tools` can also install Zookeeper or Consul for you, which requires additional dependencies. +* Vitess currently has some additional tests written in Python, but we will be skipping this step for simplicity. ### Disable mysqld AppArmor Profile @@ -75,14 +75,12 @@ Running the testsuite requires that you [install Docker](https://docs.docker.com ## Build Vitess -Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo. After doing so, navigate to the `src/vitess.io/vitess` directory. +Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo: ``` -mkdir -p ~/vitess -cd ~/vitess -git clone https://github.com/vitessio/vitess.git \ - src/vitess.io/vitess -cd src/vitess.io/vitess +cd ~ +git clone https://github.com/vitessio/vitess.git +cd vitess ``` Set environment variables that Vitess will require. It is recommended to put these in your `.bashrc`: @@ -95,27 +93,27 @@ export PATH=$PATH:/usr/local/go/bin # Vitess export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` -Run `bootstrap.sh` script to download additional dependencies. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`): +Build Vitess: ``` -BUILD_PYTHON=0 BUILD_JAVA=0 ./bootstrap.sh +make build ``` -Build Vitess: +## Testing your Binaries + +The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: ``` -source ./dev.env -make build +make tools +make test ``` -## Testing your Binaries +## Running the local example -Run the included local example: +In addition to running tests, you can try running the [local example](../../get-started/local): ``` cd examples/local @@ -167,16 +165,6 @@ Access vtgate at http://ubuntu:15001/debug/status You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. -### Full testsuite - -To run the testsuite in Docker: - -``` -make docker_test flavor=mysql57 -``` - -Running the full suite currently takes 2+ hours to complete. - ## Common Build Issues ### Key Already Exists @@ -245,14 +233,12 @@ cat: /dist/etcd/.installed_version: No such file or directory Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` ### Cannot create dir /etcd -This indicates that the environment variable `VTDATAROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: +This indicates that the environment variable `VTROOT` is not defined, and you have not put the required vitess environment variables in your `.bashrc` file: ``` ./101_initial_cluster.sh @@ -263,8 +249,6 @@ mkdir: cannot create directory ‘/etcd’: Permission denied Make sure the following variables are defined: ``` export VTROOT=~/vitess -export VTTOP=~/vitess/src/vitess.io/vitess -export VTDATAROOT=~/vitess/vtdataroot export PATH=${VTROOT}/bin:${PATH} ``` From 1d57bc15094b2d1b4c0acb6413b3c88893b877b3 Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Sun, 8 Dec 2019 11:55:07 -0700 Subject: [PATCH 2/3] Expand make test coverage Signed-off-by: Morgan Tocker --- .../en/docs/contributing/build-on-centos.md | 68 ++--------------- .../en/docs/contributing/build-on-macos.md | 76 +++---------------- .../en/docs/contributing/build-on-ubuntu.md | 73 ++---------------- 3 files changed, 27 insertions(+), 190 deletions(-) diff --git a/content/en/docs/contributing/build-on-centos.md b/content/en/docs/contributing/build-on-centos.md index d4582b4ae..e83d4dc25 100644 --- a/content/en/docs/contributing/build-on-centos.md +++ b/content/en/docs/contributing/build-on-centos.md @@ -17,8 +17,8 @@ The following has been verified to work on __CentOS 7__. If you are new to Vites [Download and install](http://golang.org/doc/install) the latest version of Golang. For example, at writing: ``` -curl -O https://dl.google.com/go/go1.13.3.linux-amd64.tar.gz -sudo tar -C /usr/local -xzf go1.13.3.linux-amd64.tar.gz +curl -O https://dl.google.com/go/go1.12.14.linux-amd64.tar.gz +sudo tar -C /usr/local -xzf go1.12.14.linux-amd64.tar.gz ``` Make sure to add go to your bashrc: @@ -85,72 +85,20 @@ make build ## Testing your Binaries -The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: +The unit tests require the following additional packages: ``` -make tools -make test -``` - -## Running the local example - -In addition to running tests, you can try running the [local example](../../get-started/local): - -``` -cd examples/local -./101_initial_cluster.sh +sudo yum install -y ant maven zip gcc ``` +You can then install additional components from `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: -You should see the following: ``` -$ ./101_initial_cluster.sh -[morgo@localhost local]$ ./101_initial_cluster.sh -enter etcd2 env -add /vitess/global -add /vitess/zone1 -add zone1 CellInfo -etcd start done... -enter etcd2 env -Starting vtctld... -Access vtctld web UI at http://localhost:15000 -Send commands with: vtctlclient -server localhost:15999 ... -enter etcd2 env -Starting MySQL for tablet zone1-0000000100... -Starting MySQL for tablet zone1-0000000101... -Starting MySQL for tablet zone1-0000000102... -Starting vttablet for zone1-0000000100... -Access tablet zone1-0000000100 at http://localhost:15100/debug/status -Starting vttablet for zone1-0000000101... -Access tablet zone1-0000000101 at http://localhost:15101/debug/status -Starting vttablet for zone1-0000000102... -Access tablet zone1-0000000102 at http://localhost:15102/debug/status -Waiting for tablets to be listening... -Tablets up! -W1028 09:30:40.634534 7333 main.go:64] W1028 15:30:40.630786 reparent.go:182] master-elect tablet zone1-0000000100 is not the shard master, proceeding anyway as -force was used -W1028 09:30:40.634792 7333 main.go:64] W1028 15:30:40.631267 reparent.go:188] master-elect tablet zone1-0000000100 is not a master in the shard, proceeding anyway as -force was used -New VSchema object: -{ - "tables": { - "corder": { - - }, - "customer": { - - }, - "product": { - - } - } -} -If this is not what you expected, check the input data (as JSON parsing will skip unexpected fields). -enter etcd2 env -Waiting for vtgate to be up... -vtgate is up! -Access vtgate at http://localhost:15001/debug/status +make tools +make test ``` -You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. +In addition to running tests, you can try running the [local example](../../get-started/local). ## Common Build Issues diff --git a/content/en/docs/contributing/build-on-macos.md b/content/en/docs/contributing/build-on-macos.md index eac58ea48..8105c1092 100644 --- a/content/en/docs/contributing/build-on-macos.md +++ b/content/en/docs/contributing/build-on-macos.md @@ -20,7 +20,7 @@ The following has been verified to work on __macOS Mojave__. If you are new to V [Install Homebrew](http://brew.sh/). From here you should be able to install: ``` -brew install go automake git curl wget mysql@5.7 etcd +brew install go@1.12 automake git curl wget mysql@5.7 etcd ``` Add `mysql@5.7` to your `PATH`: @@ -30,10 +30,6 @@ echo 'export PATH="/usr/local/opt/mysql@5.7/bin:$PATH"' >> ~/.bash_profile Do not setup MySQL or etcd to restart at login. -### Install Docker - -Running the testsuite requires that you [install Docker](https://docs.docker.com/docker-for-mac/). Should you decide to skip this step, you will still be able to compile and run Vitess. - ## Build Vitess Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo: @@ -60,69 +56,27 @@ make build ## Testing your Binaries -The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: +The unit tests require that you first install a Java runtime. This is required for running ZooKeeper tests: ``` -make tools -make test +brew tap adoptopenjdk/openjdk +brew cask install adoptopenjdk8 +brew cask info java ``` -## Running the local example - -In addition to running tests, you can try running the [local example](../../get-started/local): - +You will also need to install `ant`: ``` -cd examples/local -./101_initial_cluster.sh +brew install ant ``` - -You should see the following: +You can then install additional components from `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: ``` -$ ./101_initial_cluster.sh -morgans-mini:local morgo$ ./101_initial_cluster.sh -enter etcd2 env -add /vitess/global -add /vitess/zone1 -add zone1 CellInfo -etcd start done... -enter etcd2 env -Starting vtctld... -Access vtctld web UI at http://morgans-mini.lan:15000 -Send commands with: vtctlclient -server morgans-mini.lan:15999 ... -enter etcd2 env -Starting MySQL for tablet zone1-0000000100... -Starting MySQL for tablet zone1-0000000101... -Starting MySQL for tablet zone1-0000000102... -Starting vttablet for zone1-0000000100... -Access tablet zone1-0000000100 at http://morgans-mini.lan:15100/debug/status -Starting vttablet for zone1-0000000101... -Access tablet zone1-0000000101 at http://morgans-mini.lan:15101/debug/status -Starting vttablet for zone1-0000000102... -Access tablet zone1-0000000102 at http://morgans-mini.lan:15102/debug/status -W1027 20:11:49.555831 35859 main.go:64] W1028 02:11:49.555179 reparent.go:182] master-elect tablet zone1-0000000100 is not the shard master, proceeding anyway as -force was used -W1027 20:11:49.556456 35859 main.go:64] W1028 02:11:49.556135 reparent.go:188] master-elect tablet zone1-0000000100 is not a master in the shard, proceeding anyway as -force was used -New VSchema object: -{ - "tables": { - "corder": { - - }, - "customer": { - - }, - "product": { - - } - } -} -If this is not what you expected, check the input data (as JSON parsing will skip unexpected fields). -enter etcd2 env -Access vtgate at http://morgans-mini.lan:15001/debug/status +make tools +make test ``` -You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. +In addition to running tests, you can try running the [local example](../../get-started/local). ## Common Build Issues @@ -134,14 +88,6 @@ Error: 105: Key already exists (/vitess/zone1) [6] Error: 105: Key already exists (/vitess/global) [6] ``` -### Python Errors - -The end-to-end test suite currently requires Python 2.7. We are working on removing this dependency, but in the mean time you can run tests from within Docker. The MySQL 5.7 container provided includes the required dependencies: - -``` -make docker_test flavor=mysql57 -``` - ### No .installed_version file This error indicates that you have not put the required vitess environment variables in your `.bashrc` file: diff --git a/content/en/docs/contributing/build-on-ubuntu.md b/content/en/docs/contributing/build-on-ubuntu.md index c12267758..5d00f0e70 100644 --- a/content/en/docs/contributing/build-on-ubuntu.md +++ b/content/en/docs/contributing/build-on-ubuntu.md @@ -17,8 +17,8 @@ The following has been verified to work on __Ubuntu 19.10__ and __Debian 10__. I [Download and install](http://golang.org/doc/install) the latest version of Golang. For example, at writing: ``` -curl -O https://dl.google.com/go/go1.13.3.linux-amd64.tar.gz -sudo tar -C /usr/local -xzf go1.13.3.linux-amd64.tar.gz +curl -O https://dl.google.com/go/go1.12.14.linux-amd64.tar.gz +sudo tar -C /usr/local -xzf go1.12.14.linux-amd64.tar.gz ``` Make sure to add go to your bashrc: @@ -69,10 +69,6 @@ The following command should return an empty result: sudo aa-status | grep mysqld ``` -### Install Docker - -Running the testsuite requires that you [install Docker](https://docs.docker.com/install/). Should you decide to skip this step, you will still be able to compile and run Vitess. - ## Build Vitess Navigate to the directory where you want to download the Vitess source code and clone the Vitess GitHub repo: @@ -104,66 +100,21 @@ make build ## Testing your Binaries -The unit test requires that you first install some additional components via `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: +The unit test requires that you first install the following packages: ``` -make tools -make test +sudo apt-get install -y ant maven default-jdk zip ``` -## Running the local example - -In addition to running tests, you can try running the [local example](../../get-started/local): +You can then install additional components from `make tools`. If your machine requires a proxy to access the Internet, you will need to set the usual environment variables (e.g. `http_proxy`, `https_proxy`, `no_proxy`) first: ``` -cd examples/local -./101_initial_cluster.sh +make tools +make test ``` -You should see the following: -``` -$ ./101_initial_cluster.sh -enter etcd2 env -add /vitess/global -add /vitess/zone1 -add zone1 CellInfo -etcd start done... -enter etcd2 env -Starting vtctld... -Access vtctld web UI at http://ubuntu:15000 -Send commands with: vtctlclient -server ubuntu:15999 ... -enter etcd2 env -Starting MySQL for tablet zone1-0000000100... -Starting MySQL for tablet zone1-0000000101... -Starting MySQL for tablet zone1-0000000102... -Starting vttablet for zone1-0000000100... -Access tablet zone1-0000000100 at http://ubuntu:15100/debug/status -Starting vttablet for zone1-0000000101... -Access tablet zone1-0000000101 at http://ubuntu:15101/debug/status -Starting vttablet for zone1-0000000102... -Access tablet zone1-0000000102 at http://ubuntu:15102/debug/status -W1027 18:52:14.592776 6426 main.go:64] W1027 18:52:14.591918 reparent.go:182] master-elect tablet zone1-0000000100 is not the shard master, proceeding anyway as -force was used -W1027 18:52:14.600737 6426 main.go:64] W1027 18:52:14.594334 reparent.go:188] master-elect tablet zone1-0000000100 is not a master in the shard, proceeding anyway as -force was used -New VSchema object: -{ - "tables": { - "corder": { - - }, - "customer": { - - }, - "product": { - - } - } -} -If this is not what you expected, check the input data (as JSON parsing will skip unexpected fields). -enter etcd2 env -Access vtgate at http://ubuntu:15001/debug/status -``` +In addition to running tests, you can try running the [local example](../../get-started/local). -You can continue the remaining parts of this example by following the [local](../../get-started/local) get started guide. ## Common Build Issues @@ -213,14 +164,6 @@ export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh ``` -### Python Errors - -The end-to-end test suite currently requires Python 2.7. We are working on removing this dependency, but in the mean time you can run tests from within Docker. The MySQL 5.7 container provided includes the required dependencies: - -``` -make docker_test flavor=mysql57 -``` - ### No .installed_version file This error indicates that you have not put the required vitess environment variables in your `.bashrc` file: From 144d62d1330e3706b7a7fdfe23126e8dda97d9d0 Mon Sep 17 00:00:00 2001 From: Morgan Tocker Date: Sun, 8 Dec 2019 15:55:39 -0700 Subject: [PATCH 3/3] Fix macOS path for golang Signed-off-by: Morgan Tocker --- content/en/docs/contributing/build-on-macos.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/contributing/build-on-macos.md b/content/en/docs/contributing/build-on-macos.md index 8105c1092..1e5cb5bb9 100644 --- a/content/en/docs/contributing/build-on-macos.md +++ b/content/en/docs/contributing/build-on-macos.md @@ -23,9 +23,10 @@ The following has been verified to work on __macOS Mojave__. If you are new to V brew install go@1.12 automake git curl wget mysql@5.7 etcd ``` -Add `mysql@5.7` to your `PATH`: +Add `mysql@5.7` and `go@1.12` to your `PATH`: ``` echo 'export PATH="/usr/local/opt/mysql@5.7/bin:$PATH"' >> ~/.bash_profile +echo 'export PATH="/usr/local/opt/go@1.12/bin:$PATH"' >> ~/.bash_profile ``` Do not setup MySQL or etcd to restart at login.