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

chore(acceptance): add tests for PSM to z:acceptance #3

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

anilhelvaci
Copy link
Collaborator

Refs: https://github.com/Agoric/BytePitchPartnerEng/issues/23

closes: #XXXX
refs: #XXXX

Description

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Upgrade Considerations

@anilhelvaci anilhelvaci force-pushed the anil/psm-tests branch 4 times, most recently from 0c1ae50 to 3b48050 Compare October 19, 2024 07:07
frazarshad and others added 11 commits October 24, 2024 19:52
…0241)

closes: Agoric#10138 
closes: Agoric#10185 
closes: Agoric#10258
## Description

A3P tests for the replace electorate core eval. also adds the replace-electorate-core.js script to upgrade.go since it will now be a part of the chain halting upgrade

new tests are as follows:
- adds new `n:replace-electorate` which tests for acceptance of new invitations
- adds params governance proposal and voting tests to `z:acceptance`

### Security Considerations


### Scaling Considerations


### Documentation Considerations


### Testing Considerations


### Upgrade Considerations
refs: Agoric#10267

## Description

We'll be upgrading Zoe in the next SW upgrade. We need to reset the KREAd subscribers when we do that.

### Security Considerations

No broader security implications

### Scaling Considerations

Not a scaling concern

### Documentation Considerations

I should have remembered this when adding the Zoe upgrade.

### Testing Considerations

None

### Upgrade Considerations

There's a constraint that we need to enforce when we upgrade Zoe. So far, we've been remembering it, but it would be better to automate.
…ic#10306)

closes: Agoric#10274

## Description

Half the EC were able to pass a motion, when a majority should have been required.

### Security Considerations

Ordinary vote counting issue.

### Scaling Considerations

N/A

### Documentation Considerations

None

### Testing Considerations

Added tests for committee.

### Upgrade Considerations

The change is in the committee code. This needs to be merged before the proposal in Agoric#10164 runs. It [already installs new committee code](https://github.com/Agoric/agoric-sdk/blob/4a33accaeeba27044ab07dd04f64226de1b77759/packages/builders/scripts/inter-protocol/replace-electorate-core.js#L28).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants