cerc-io/laconicd
18
0
Fork 1
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

laconic-sdk tests in CI #46

New Issue
Closed
opened 2022-11-03 13:19:53 +00:00 by i-norden · 5 comments
i-norden commented 2022-11-03 13:19:53 +00:00
Member
Copy Link

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.
i-norden commented 2022-12-08 16:44:56 +00:00
Author
Member
Copy Link

@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
i-norden commented 2022-12-20 14:14:52 +00:00
Author
Member
Copy Link

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.
dboreham commented 2022-12-21 20:56:43 +00:00
Owner
Copy Link

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)
Copy Link

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)
Copy Link

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 Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
C:CLI

   
C:Crypto

   
C:Encoding

   
C:Proto

   
C:Types

   
dependencies

Pull requests that update a dependency file

  
docker

Pull requests that update Docker code

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
go

Pull requests that update Go code

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
high priority

   
in progress

currently working on

  
invalid

This doesn't seem right

  
javascript

Pull requests that update Javascript code

  
low priority

   
medium priority

   
question

Further information is requested

  
Status: Stale

   
Type: ADR

   
Type: Build

   
Type: CI

   
Type: Docs

   
Type: Tests

   
urgent

Top priority issue

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

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 Label
bug
C:CLI
C:Crypto
C:Encoding
C:Proto
C:Types
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
high priority
in progress
invalid
javascript
low priority
medium priority
question
Status: Stale
Type: ADR
Type: Build
Type: CI
Type: Docs
Type: Tests
urgent
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#46
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?