laconic-sdk tests in CI #46
Closed
opened 2022-11-03 13:19:53 +00:00 by i-norden
·
5 comments
No Branch/Tag Specified
main
zach/prefix
roy/rm-hardcoded-records
roy/graphql-to-ipld
roy/qol-improvements
murali/gql
murali/update-fork
murali/record-attributes
aleem/fix-lint-errors
murali/CIDFromJSONBytes
update-validator-doc-v0.8.0
feature_test_record_types
aleem/25-wasmd
release-v0.8.0
nameservice_tests_github
auction_tests
all_test_stuff
fix_cid_generation
run_tests_github_action
0-7-0-upgrade-guide
murali/sdk-integration-tests
murali/quick-fix
dboreham/sdk-integration-test
console_release
release-v0.3.1-dev
release-v0.6.0
anil/lint
murali/to_ipld_prime
docs
release-v0.2.0-dev
ian/smt
v0.8.0
v0.7.0
v0.6.0
v0.3.0-dev
v0.2.1-dev
v0.2.0-dev
v0.1.0-dev
Labels
Clear labels
C:CLI
C:Crypto
C:Encoding
C:Proto
C:Types
Status: Stale
Type: ADR
Type: Build
Type: CI
Type: Docs
Type: Tests
bug
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
high priority
in progress
invalid
javascript
low priority
medium priority
question
urgent
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Something isn't working
Pull requests that update a dependency file
Pull requests that update Docker code
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Pull requests that update Go code
Good for newcomers
Extra attention is needed
currently working on
This doesn't seem right
Pull requests that update Javascript code
Further information is requested
Top priority issue
This will not be worked on
An issue or PR manually copied from GitHub.
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Type: CI
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/laconicd-deprecated#46
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
@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
Have CD for a container that incorporates the built cosmos-sdk, such that anybody can pull that container with the
latesttag and execute with adocker runcommand.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.
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.
Tests pass locally, but failing in CI is masked by docker logs output.
Doubling bond in naming tests from sdk side get tests passing.