-
Notifications
You must be signed in to change notification settings - Fork 208
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
base upgrade-next on top of latest (use-upgrade-14) #9204
Conversation
:latest was bumped to include u14 by Agoric/agoric-3-proposals#141 but master can't yet apply on top of u14 #9204
8172a44
to
27827ab
Compare
failing in
|
I'm happy to see this. I'll wait for tests to turn green before rebasing my upgrade-next work to it. |
27827ab
to
fcb0070
Compare
Deploying agoric-sdk with Cloudflare Pages
|
Gas is solved by using syntheti-chain 0.0.9. Now it's failing on this in
@Chris-Hibbert PTAL |
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 remove the core eval submission test?
bc I thought it was part of u14. (see test: remove upgrade-14 content from upgrade-next ) if that's not correct, please request the change or push a fixup |
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.
Let's keep the core-eval test, it's currently the only integration test we have for #8884
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.
Let's keep this test around, it's not specific to any upgrade.
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.
Oh good point about moving it to a z:acceptance
layer! I think we can have "test only" layers now?
Edit: not officially, but we can have a /agoric.swingset.CoreEvalProposal
which has a eval.sh
script that does nothing.
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.
More changes needed in the plumbing of upgrade info due to sdk 0.46 changes
Yep. The test that the walletFactory upgrade was successful fails because that upgrade failed. Stack trace
I'm investigating... |
34327ff
to
fb74bbd
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.
I reviewed and Approve. I opened the PR so GH won't let that count. @mhofman if you approve you can merge.
@@ -1,3 +1,5 @@ | |||
# syntax=docker/dockerfile:1.4 |
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.
what happens without 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.
My docker engine won't grok --link
directives without it.
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.
@@ -48,7 +48,9 @@ export const probeZcfBundleCap = async ( | |||
await E(adminNode).upgrade(zoeBundleCap, {}); | |||
|
|||
// STEP 4: restart WF //////////////////////// | |||
await E(walletAdminFacet).restartContract(privateArgs); | |||
// Need to use `upgradeContract` instead of `restartContract` | |||
// See https://github.com/Agoric/agoric-sdk/issues/9249 |
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.
ahh
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.
Carrying @turadg approval of the final changes
initial.test.js copied from #9204
initial.test.js copied from #9204, minus checks for "network" and "localchain" vats (which on master are installed by core proposals).
initial.test.js copied from #9204, minus vats that are missing in the release-mainnet1B image.
closes: #9206
Description
With Agoric/agoric-3-proposals#141
a3p:latest
now includesdev-upgrade-14
branch's upgrade handler. This removes the redundant parts from the UNRELEASED upgrade handler and its tests in a3p-integration.It also introduces a convention
initial.test.js
to make clear what tests are of the post-upgrade state, to be run before tests that can modify the state. Another option is to number the tests so they run in order. I figure this can happen when needed; the test.sh allows any logic.Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
no
Testing Considerations
Tests
Upgrade Considerations
Upgrade tests