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

Pruning Testing Checklist #3958

Closed
4 tasks done
shekhirin opened this issue Jul 27, 2023 · 1 comment
Closed
4 tasks done

Pruning Testing Checklist #3958

shekhirin opened this issue Jul 27, 2023 · 1 comment
Labels
A-pruning Related to pruning or full node C-test A change that impacts how or what we test S-stale This issue/PR is stale and will close with no further activity

Comments

@shekhirin
Copy link
Collaborator

shekhirin commented Jul 27, 2023

Describe the feature

When #3428 is done, we need to test different scenarios, e.g.:

  1. Archive -> Full Node
  2. Full Node from scratch
  3. Archive -> Partly pruned node

And, most importantly, we need to check that RPCs, Engine API and other important parts work as expected (with restrictions due to pruning applied).

Sync

Preview Give feedback

RPC

Preview Give feedback

Additional context

No response

@shekhirin shekhirin added C-test A change that impacts how or what we test A-pruning Related to pruning or full node labels Jul 27, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label Aug 22, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-pruning Related to pruning or full node C-test A change that impacts how or what we test S-stale This issue/PR is stale and will close with no further activity
Projects
Archived in project
Development

No branches or pull requests

1 participant