5.4 KiB

Raw Blame History

Integration between nimbus-eth1 and Ethereum Hive test environment

This is a short manual to help you quickly setup and run Hive. For more detailed information please read the hive documentation.

Prerequisities

A Linux machine. Trust me, it does not work on Windows or MacOS.
Or Linux inside a VM (e.g. VirtualBox) on Windows or MacOS.
Docker installed and working in your Linux.
Go compiler installed in your Linux.
Go must be version 1.16 or later.

Practicalities

Practically, if using an Ubuntu Linux and you want to use the version of Go shipped with Ubuntu, you will need Ubuntu 21.04 or later. It's enough to run apt-get install golang.

If using Ubuntu 20.04 LTS (likely because it's the long-term stable version), the shipped Go isn't recent enough, and there will be build errors. You can either install a non-Ubuntu packaged version of Go (maybe from golang.org, or use a more recent Ubuntu.

If you want to run Hive in a Linux container, you will need Docker to work in the container because Hive calls Docker (a lot!). This is sometimes called "Docker in Docker". Inside LXD containers, Docker doesn't work by default, but usually this is remedied by setting the container flag lxc config set $CONTAINER_NAME security.nesting true, which takes effect immediately.

Building hive

First you will need a working Go installation, Go 1.16 or later. Then:

git clone https://github.com/ethereum/hive
cd ./hive
go build .

How to run hive

First copy the nimbus-eth1/hive_intgration/nimbus folder (from this repo) into the hive/clients folder (in the hive repo).

Then run this command:

./hive --sim <simulation> --client <client(s) you want to test against>

Examples:

./hive --sim ethereum/consensus --client nimbus

./hive --sim devp2p/discv4 --client go-ethereum,openethereum,nimbus

Available test suites / simulators

devp2p/eth
devp2p/discv4
ethereum/sync
ethereum/consensus
ethereum/rpc
ethereum/graphql
smoke/network
smoke/genesis
smoke/clique

Current state of the tests

These Hive suites/simulators can be run:

ethereum/consensus
ethereum/graphql
ethereum/rpc
smoke/network
smoke/genesis

These Hive suites/simulators don't work with nimbus-eth1 currently:

devp2p/discv4
devp2p/eth
ethereum/sync
smoke/clique

The number of passes and fails output at the time of writing (2021-05-18) is:

ethereum/consensus:  28186 pass,    59 fail, 28245 total
ethereum/graphql:       36 pass,    10 fail,    46 total
devp2p/discv4:           0 pass,    14 fail,    14 total
devp2p/eth:              0 pass,     1 fail,     1 total
ethereum/rpc:            3 pass,    35 fail,    38 total
ethereum/sync:           0 pass,     1 fail,     1 total
smoke/genesis:           3 pass,     0 fail,     3 total
smoke/network:           1 pass,     0 fail,     1 total
smoke/clique:            0 pass,     1 fail,     1 total

Nim simulators without docker

We have rewrite some of the hive simulators in Nim to aid debugging. It is assumed you already install nimbus dependencies via nimble. In the future, we will provide more instructions how to run these simulators using local dependencies.

On Windows you might need to add -d:disable_libbacktrace compiler switch. Working directory is nimbus-eth1 root directory. And you can see the result in a markdown file with the same name with the simulator.

ethereum/consensus

first you need to run extract_consensus_data

nim c -r -d:release hive_integration/nodocker/consensus/extract_consensus_data

then you can run the simulator

nim c -r -d:release hive_integration/nodocker/consensus/consensus_sim

ethereum/graphql

nim c -r -d:release hive_integration/nodocker/graphql/graphql_sim

Observations when working with hive/docker

DNS problems with hive simulation container running alpine OS

Problem:
hive bails out with error when compiling docker compile because it cannot resolve some domain name like github.com. It occured with a locally running DNS resolver (as opposed to a proxy type resolver.)
Solution:
- First solution (may be undesirable): Change local nameserver entry in /etc/resolv.conf to something like
```
   nameserver 8.8.8.8
```
  Note that docker always copies the host's /etc/resolv.conf to the container one before it executes a RUN directive.
- Second solution (tedious): In the Dockerfile, prefix all affected RUN directives with the text:
```
   echo nameserver 8.8.8.8 > /etc/resolv.conf;
```

Peek into nimbus container before it finalises

In the nimbus Dockerfile before ENTRYPOINT, add the directive

     RUN mknod /tmp/wait-for-stop p;cat /tmp/wait-for-stop

(Re-)Build the container with the command:
```
     ./hive --docker.output ...
```
When the building process hangs at the
```
      RUN mknod ...
```
directive, then use the ./docker-shell script to enter the running top docker container

Useful commands after entering the nimbus container

     apt udate
     apt install iproute2 procps vim openssh-client strace

Resume hive installation & processing:
In the nimbus container run
```
     echo > /tmp/wait-for-stop
```

5.4 KiB Raw Blame History