infra: hive forking and tuning

Bidon15 commented 3 years ago

We need to revisit what is needed in the repo, to define what

[ ] can be used for out testing needs
[ ] should be removed in the present state of the repo
[ ] functionality is lacking to achieve our testing needs
[ ] dashboard to track em(tests) all

Bidon15 commented 3 years ago

Try to poke celestia-core to know what to strip and what to tune Instead of using dummy-app -> use real celetia-app

What to look for https://github.com/celestiaorg/lazyledger-app/issues/39

Bidon15 commented 3 years ago

We discovered some weird behaviour of hive when tests were being executed during our debugging session on 26/10/21. The only error log message looks like this Post "http://172.17.0.1:38957/testsuite": dial tcp 172.17.0.1:38957: i/o timeout

Reproduced with using our clients/sims as well as eth's.

This is blocking us from actually verifying if something is being tested during/after runtime due to absence of meaningful logs. This requires even further deep diving into finding the root cause and we made a decision to replace hive for devnet and use another approach(vanilla docker compose, dockertest or testground).

Bidon15 commented 2 years ago

closing in favour of testground and swamp

celestiaorg / test-infra

infra: hive forking and tuning #3