test: run e2e test of ceremony in CI #3204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Error
redshiftzero
force-pushed
the
ci-int-summonerd
branch
from
8ba0736 to
8957bc8
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Error
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
force-pushed
the
ci-int-summonerd
branch
from
8957bc8 to
552fea9
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Error
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
force-pushed
the
ci-int-summonerd
branch
from
29fdb0d to
1286298
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
force-pushed
the
ci-int-summonerd
branch
from
1286298 to
94ce16c
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
phase 1 is super slow, this job will take forever with multiple accounts
Unfortunately we also need the devnet to be running because the summonerd e2e test takes a while and testnet preview might be redeployed during the run. That means that we need to run against a devnet that we _know_ will be stable.
redshiftzero
force-pushed
the
ci-int-summonerd
branch
from
94ce16c to
f548956
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3189
Thanks to #3208 the runtime of this went from ~60m down to ~18m! One can see a successful run of the CI job here which was executed on the second to last commit here: f548956.
I've used the
workflow_dispatchoption to only run this job on demand (will work once the CI job is on the default branch), and on merges intomain. It may make sense later to run the job only nightly/weekly instead of every merge intomain, but while the summoner is under active development I think running on merge intomainis reasonable.