-
Notifications
You must be signed in to change notification settings - Fork 7
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
Make runner compatible with wide range of SDK revisions #37
Conversation
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.
LGTM!
Straightforward, but lots of details. I tried mainly to make sure your way of starting up the chain and provisioning matched with my understanding, which it does.
runner/lib/tasks/local-chain.js
Outdated
await fs.stat(name); | ||
return true; | ||
} catch (e) { | ||
return 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 would mildly prefer:
return false; | |
if (e.code === 'ENOENT') { | |
return false; | |
} | |
throw e; |
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.
Agreed, but to be fair this is ripped straight from agoric-cli
:
bc973f6
to
6b1e31e
Compare
4d96e29
to
541e6a8
Compare
b2b3005
to
dbf3f59
Compare
541e6a8
to
6ff64f6
Compare
dbf3f59
to
1e66f9e
Compare
@michaelfig I addressed your feedback in ec62441 and made a small further change in 1e66f9e. Will carry your previous approval, squash and merge. |
1e66f9e
to
2e870bc
Compare
add devnet profile and shared save-storage options
Do not set loadgen config if no active loadgen requested
When I started regenerating the corpus of stats, I realized that the runner and loadgen did not run correctly against both older and newer SDK revisions (I was working against a somewhat outdated version).
In particular:
The first issue is fixed by provisioning and starting the local-solo manually, which required hooking into the cli to figure out the right path to use across revisions.
The second issue is addressed by winding down the loadgen before shutting everything down. The issue has since been fixed in the agoric-sdk (Agoric/agoric-sdk#4116), but the workaround is left for older revisions, and is made configurable if we want to test for regressions.
For the last issue, the default config moves the wallet and loadgen deployments to stage 0, which is now truly a full setup stage.
As always, best reviewed commit-by-commit.
Stacks on top of the stats work (#36).