laconic-sdk tests in CI #46

Closed
opened 2022-11-03 13:19:53 +00:00 by i-norden · 5 comments
Member

Run laconic-sdk test suite against laconicd docker image in CI.

The plan here is to add laconic-sdk as a repo dependency in the CI environment, the CI will build the tests from there and run them against the new version of laconicd.

Run these tests on PRs to main and releases.

Run [laconic-sdk](https://github.com/cerc-io/laconic-sdk#tests) test suite against laconicd docker image in CI. The plan here is to add laconic-sdk as a repo dependency in the CI environment, the CI will build the tests from there and run them against the new version of laconicd. Run these tests on PRs to main and releases.
Author
Member

@ABastionOfSanity in light of https://github.com/cerc-io/laconic-sdk/issues/8 figuring out how to run the laconic-sdk tests in CI is pretty high priority imo

@ABastionOfSanity in light of https://github.com/cerc-io/laconic-sdk/issues/8 figuring out how to run the laconic-sdk tests in CI is pretty high priority imo
Author
Member

Have CD for a container that incorporates the built cosmos-sdk, such that anybody can pull that container with the latest tag and execute with a docker run command.

This will work unless you are making breaking changes on laconicd, which require changes to comsos-sdk. For this scenario it would be helpful to be able to target the CD to a specific commit/branch/release of laconicd.

Have CD for a container that incorporates the built cosmos-sdk, such that anybody can pull that container with the `latest` tag and execute with a `docker run` command. This will work unless you are making breaking changes on laconicd, which require changes to comsos-sdk. For this scenario it would be helpful to be able to target the CD to a specific commit/branch/release of laconicd.
Owner

See: https://github.com/cerc-io/laconicd/pull/71
In that PR I have running the test suite in a containerized network working. However the tests fail. Why, TBD.

See: https://github.com/cerc-io/laconicd/pull/71 In that PR I have running the test suite in a containerized network working. However the tests fail. Why, TBD.
ABastionOfSanity commented 2023-02-07 20:25:25 +00:00 (Migrated from github.com)

Tests pass locally, but failing in CI is masked by docker logs output.

Tests pass locally, but failing in CI is masked by docker logs output.
ABastionOfSanity commented 2023-02-09 20:28:53 +00:00 (Migrated from github.com)

Doubling bond in naming tests from sdk side get tests passing.

Doubling bond in naming tests from sdk side get tests passing.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconicd-deprecated#46
No description provided.