Skip to content
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

facility for testing MN-2 partner contracts in chain upgrade tests #8376

Closed
1 task done
turadg opened this issue Sep 23, 2023 · 2 comments · Fixed by Agoric/agoric-3-proposals#16
Closed
1 task done
Assignees
Labels
enhancement New feature or request

Comments

@turadg
Copy link
Member

turadg commented Sep 23, 2023

What is the Problem Being Solved?

Our docker-based upgrade-tests are our only way in CI to verify that new proposals against (approximate) Mainnet will succeed.

Partner proposals (outside agoric-sdk) change Mainnet too and must be included in the history.

Description of the Design

Some way for agoric-sdk to fetch manifests and bundles from partner proposals.

And/or a new repo outside of agoric-sdk that tests chain upgrades against a history.

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

@turadg turadg added the enhancement New feature or request label Sep 23, 2023
@dckc dckc self-assigned this Oct 4, 2023
@dckc
Copy link
Member

dckc commented Oct 23, 2023

@turadg and I plan to land this in a separate repo (#8443)

@dckc
Copy link
Member

dckc commented Nov 8, 2023

The agoric-3-proposals design seems to suffice; we have 2 CoreEval proposals working:

@dckc dckc closed this as completed Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants