Skip to content

[antithesis] randomize checkpoint split limit for reachability assert#25364

Merged
alex-mysten merged 3 commits intomainfrom
steka-antithesis-cp-split-reachability
Feb 25, 2026
Merged

[antithesis] randomize checkpoint split limit for reachability assert#25364
alex-mysten merged 3 commits intomainfrom
steka-antithesis-cp-split-reachability

Conversation

@alex-mysten
Copy link
Copy Markdown
Contributor

@alex-mysten alex-mysten commented Feb 9, 2026

Description

Lower the checkpoint split limit so we can assert reachability

Test plan

steka-antithesis-cp-split-reachability 3430e844 4.0h
steka-antithesis-cp-split-reachability mainnet upgrade split-version 4.0h


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

  • Protocol: test only changes, no user impact
  • Nodes (Validators and Full nodes):
  • gRPC:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:
  • Indexing Framework:

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 25, 2026 1:40am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
multisig-toolkit Ignored Ignored Preview Feb 25, 2026 1:40am
sui-kiosk Ignored Ignored Preview Feb 25, 2026 1:40am

Request Review

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 9, 2026 4:25pm

Request Review

4 similar comments
@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 9, 2026 4:25pm

Request Review

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 9, 2026 4:25pm

Request Review

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 9, 2026 4:25pm

Request Review

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 9, 2026 4:25pm

Request Review

@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 11, 2026 19:53 — with GitHub Actions Inactive
@alex-mysten alex-mysten changed the title [antithesis] lower checkpoint split limit for reachability assert [antithesis] randomize checkpoint split limit for reachability assert Feb 11, 2026
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from e8f7169 to 6666f50 Compare February 11, 2026 20:22
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 11, 2026 20:22 — with GitHub Actions Inactive
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from 6666f50 to 6a43729 Compare February 11, 2026 20:41
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 11, 2026 20:41 — with GitHub Actions Inactive
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from 6a43729 to c884bf8 Compare February 11, 2026 21:37
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 11, 2026 21:37 — with GitHub Actions Inactive
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from c884bf8 to fac24ec Compare February 12, 2026 11:06
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 12, 2026 11:06 — with GitHub Actions Inactive
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from fac24ec to 21d7e16 Compare February 12, 2026 20:04
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 12, 2026 20:04 — with GitHub Actions Inactive
@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from 21d7e16 to c6c12b0 Compare February 12, 2026 20:20
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 12, 2026 20:20 — with GitHub Actions Inactive
true
} else {
mysten_common::in_antithesis()
};
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can use mysten_common::in_test_configuration()

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed

validator_metadata_verify_v2: bool,

#[serde(skip_serializing_if = "is_false")]
randomize_checkpoint_tx_limit_in_tests: bool,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's make this a catch-all flag, randomize_params_for_tests and then below we will use this as a signal to randomize anything that it makes sense to randomize - we'll probably add more things than just this

Copy link
Copy Markdown
Contributor Author

@alex-mysten alex-mysten Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these need to be individualized for anything that is an existing protocol config.

The reason I added this is because without this we do an antithesis upgrade test, we get a fork, because the max_txns_per_checkpoint would change mid-epoch.

If we generalize this protocol config, any additional randomization we add here would also fork antithesis, as the whole block is gated by one flag.

We could also not gate it, knowing that the only risk is potentially misleading antithesis upgrade forks when we introduce new randomization.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, good point, we can also revisit this later

@alex-mysten alex-mysten force-pushed the steka-antithesis-cp-split-reachability branch from 1230db8 to 09d0f12 Compare February 25, 2026 01:38
@alex-mysten alex-mysten temporarily deployed to sui-typescript-aws-kms-test-env February 25, 2026 01:38 — with GitHub Actions Inactive
@alex-mysten alex-mysten merged commit 61c2f72 into main Feb 25, 2026
57 of 58 checks passed
@alex-mysten alex-mysten deleted the steka-antithesis-cp-split-reachability branch February 25, 2026 02:01
jessiemongeon1 pushed a commit to jessiemongeon1/sui that referenced this pull request Mar 5, 2026
…MystenLabs#25364)

## Description 

Lower the checkpoint split limit so we can assert reachability

## Test plan 

[steka-antithesis-cp-split-reachability 3430e84
4.0h](https://mystenlabs.antithesis.com/report/ZxSVmPkRhggT8uE06sAPf24U/8wWUOHsk4BFMv0hjPDJnvSqARNjVXdKcd5HoRcnWlho.html?auth=v2.public.eyJuYmYiOiIyMDI2LTAyLTE3VDAwOjUzOjA4Ljc4NDkyNTIyMloiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0IjoiOHdXVU9Ic2s0QkZNdjBoalBESm52U3FBUk5qVlhkS2NkNUhvUmNuV2xoby5odG1sIiwicmVwb3J0X2lkIjoiWnhTVm1Qa1JoZ2dUOHVFMDZzQVBmMjRVIn19fR9cbuhCp8uVXZPngeTBo1OwukkBAKAo7isIOEjEtILTkScnDPETk6NupSkMUVxkdHaKYn_LFKTeDxg3xv1l6gk)
[steka-antithesis-cp-split-reachability mainnet upgrade split-version
4.0h](https://mystenlabs.antithesis.com/report/8slJysoNBugHn_CwKruqbihm/UY_kqoRdK0Qlgz21DNY8u2dv5Dk_iGsQnDbUTfBf9fU.html?auth=v2.public.eyJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0IjoiVVlfa3FvUmRLMFFsZ3oyMUROWTh1MmR2NURrX2lHc1FuRGJVVGZCZjlmVS5odG1sIiwicmVwb3J0X2lkIjoiOHNsSnlzb05CdWdIbl9Dd0tydXFiaWhtIn19LCJuYmYiOiIyMDI2LTAyLTE3VDAxOjE4OjI1Ljc4NTAxOTI1NVoifR7ITGuMFJFEytjMk7yCqfKaVN7zs_5tZYlGqFBUA9lSXdkNtJxLpc0c_2TXCEDdsXgaiGVzf1U5wirO7FekUQw)

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [x] Protocol: test only changes, no user impact
- [ ] Nodes (Validators and Full nodes): 
- [ ] gRPC:
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:
- [ ] Indexing Framework:
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.

2 participants