sdk integration test #71

dboreham · 2022-12-21T20:55:55Z

dboreham commented

2022-12-21 20:55:55 +00:00

WIP:

This allows creation of two containers : cerc-io/laconicd:local-test , built from the current local tree and cerc-io/laconic-sdk-tester:local-test which contains the laconic-sdk project cloned from git in the container build process.

Handy scripts build-laconicd-container.sh and build-sdk-test-container.sh for building those containers.

Then you can run docker compose up -d to spin up laconicd and the test runner container networked together.

And then you run ./run-tests.sh to run the laconic-sdk test suite.

Alas at present all tests fail with:

    thrown: Array [
      Object {
        "message": "rpc error: code = NotFound desc = account ethm1zhhartn9s7xv03dze45y93nedusyhq58magakl not found",
        "path": Array [
          "getAccounts",
        ],
      },
    ]

Usually this is a symptom of the chain id being wrong. However I've corrected it (I think...) and the errors persis.
So a second cycle of debugging the failures is required.

WIP: This allows creation of two containers : `cerc-io/laconicd:local-test` , built from the current local tree and `cerc-io/laconic-sdk-tester:local-test` which contains the laconic-sdk project cloned from git in the container build process. Handy scripts `build-laconicd-container.sh` and `build-sdk-test-container.sh` for building those containers. Then you can run `docker compose up -d` to spin up laconicd and the test runner container networked together. And then you run `./run-tests.sh` to run the laconic-sdk test suite. Alas at present all tests fail with: ``` thrown: Array [ Object { "message": "rpc error: code = NotFound desc = account ethm1zhhartn9s7xv03dze45y93nedusyhq58magakl not found", "path": Array [ "getAccounts", ], }, ] ``` Usually this is a symptom of the chain id being wrong. However I've corrected it (I think...) and the errors persis. So a second cycle of debugging the failures is required.

❤️ 1

0xmuralik (Migrated from github.com) reviewed 2022-12-21 20:55:55 +00:00

0xmuralik commented

2022-12-26 06:27:30 +00:00

(Migrated from github.com)

After running docker compose up I tried to run a cli qurey to the chain and it fails
Ex: laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused
The ports might be different.

After running docker compose up I tried to run a cli qurey to the chain and it fails Ex: `laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused` The ports might be different.

dboreham commented

2022-12-26 17:28:55 +00:00

After running docker compose up I tried to run a cli qurey to the chain and it fails Ex: laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused The ports might be different.

Hmm. This works for me:

$ docker compose exec laconicd laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd
balances: []
pagination:
  next_key: null
  total: "0"

> After running docker compose up I tried to run a cli qurey to the chain and it fails Ex: `laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused` The ports might be different. Hmm. This works for me: ``` $ docker compose exec laconicd laconicd q bank balances ethm1m7cnnpqk24r42h7dt0t4d7l2qh0uw46muv4qtd balances: [] pagination: next_key: null total: "0" ```

dboreham reviewed 2022-12-28 04:53:39 +00:00

init.sh

dboreham commented

2022-12-28 04:53:39 +00:00

This is the correct chain id.

zramsay commented

2023-01-03 14:11:57 +00:00

not sure if this error is still an issue: Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused but it looked instantly familiar and this answer has worked for me in the past: https://stackoverflow.com/a/61345315

not sure if this error is still an issue: `Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refused` but it looked instantly familiar and this answer has worked for me in the past: [https://stackoverflow.com/a/61345315](https://stackoverflow.com/a/61345315)

👀 1

Sign in to join this conversation.

No reviewers

0xmuralik