-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: multichain-testing with go-relayer
#10182
base: master
Are you sure you want to change the base?
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
cd1daba
to
2d38529
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff!
|
||
- name: Setup Starship Infrastructure | ||
id: starship-infra | ||
uses: cosmology-tech/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not latest? https://github.com/cosmology-tech/starship-action/releases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I bumped to 0.5.3 here and will see what CI thinks: #10216
It looks the ability to specify a helm chart version may have been lost starting 0.5.4 (the latest is 0.5.7). I filed an cosmology-tech/starship-action#34 asking for clarification.
We can also bump the helm chart version. We're on 0.2.10 but it's up to 0.2.14. I ran into issues with the new readinessProbe
- it seem the approach we provided is not working on my local. I filed cosmology-tech/starship#563 to track this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
563 was merged last week. Let's see if we can get an answer on 34 soon enough to incorporate it
|
||
- name: Setup Starship Infrastructure | ||
id: starship-infra | ||
uses: cosmology-tech/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not latest? https://github.com/cosmology-tech/starship-action/releases
2d38529
to
a0ae81b
Compare
Hesitant to merge until we see this go through CI multiple times successfully. I was under the impression each run is fully containerized, but am seeing weird behavior which leads me to believe these are stepping on each other's toes. Both jobs read from and write to the Any folks with more gh-action-fu have more insights? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll approve when the work-arounds for upstream issues are gone, or there's a conspicuous plan for addressing them.
with: | ||
# uses ghcr.io/agoric/agoric-sdk:dev image (latest master) | ||
values: ./agoric-sdk/multichain-testing/${{ inputs.config }} | ||
port-forward: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see in the commit this is just until cosmology-tech/starship#561 is available.
That's helpful but even more important is for the source to say so, to anyone browsing who could then simplify this code.
Incidentally, isn't your PR available now in a starship release?
|
||
- name: Setup Starship Infrastructure | ||
id: starship-infra | ||
uses: cosmology-tech/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
563 was merged last week. Let's see if we can get an answer on 34 soon enough to incorporate it
multichain-testing/README.md
Outdated
@@ -90,6 +90,15 @@ kubectl logs hermes-agoric-gaia-0 --container=relayer --follow | |||
kubectl logs hermes-osmosis-gaia-0 --container=relayer --follow | |||
``` | |||
|
|||
## Running With a Different Config File |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Capital With
jarred me but I don't suppose Agoric has an agreed upon Title Case. 😂
f0827ce
to
11015a0
Compare
fa4b501
to
4414f4c
Compare
a486634
to
0cae9dd
Compare
1780dad
to
94f55f1
Compare
- currently, tests were only run using the hermes relayer. now, we test both hermes and go-relayer in CI
- fixes TypeError due to missing `/cosmos.bank.v1beta1.QueryAllBalancesRequest` key on `Proto3Shape`
- factor out to commonSetup - deleteTestKeys only removes keys present in keyring
522fc15
to
c98b29a
Compare
82709be
to
a0c73e0
Compare
closes: #10179
Description
go-relayer
)go-relayer
(config.gorelayer.yaml
)go-relayer
whenRELAYER_TYPE
env var is presentmultichain-e2e
workflow to a template and runhermes
andgo-relayer
jobs in parallelSecurity Considerations
n/a, test code
Scaling Considerations
For CI, this uses more resources. We have an additional
ubuntu-latest-16core
running and another ~30 min job (running in parallel).Documentation Considerations
Added a section in the
README.md
with instructions for running the tests withgo-relayer
.Testing Considerations
Runs existing test suite against
go-relayer
, increasing our test coverage across differing infrastructure. Should help identify any relayer-specific issues or discrepancies.Upgrade Considerations
n/a