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

test(e2e): add fee distribution test in Kroma MPT #405

Merged
merged 5 commits into from
Dec 19, 2024

Conversation

seolaoh
Copy link
Contributor

@seolaoh seolaoh commented Dec 17, 2024

Description

Added the fee distribution test in Kroma MPT.
The setup for historical RPC node and other nodes are repeated in all tests for Kroma MPT, so I added a utility function and global variable to set up MPT environment in system config setup.

@seolaoh seolaoh self-assigned this Dec 17, 2024
@seolaoh seolaoh requested a review from a team as a code owner December 17, 2024 05:10
Copy link
Contributor

coderabbitai bot commented Dec 17, 2024

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (2)
  • dev
  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@@ -1549,6 +1526,18 @@ func testFees(t *testing.T, cfg SystemConfig) {
validatorRewardVaultStartBalance, err := l2Seq.BalanceAt(context.Background(), predeploys.ValidatorRewardVaultAddr, big.NewInt(rpc.EarliestBlockNumber.Int64()))
require.Nil(t, err)

// Fee recipients after Kroma MPT
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it would be nice to have a before and after conditional block, like if !sys.RollupConfig.IsKromaMPT(header.Time), or do you have another intention?

@seolaoh seolaoh requested a review from kangsorang December 17, 2024 06:43
op-e2e/system_test.go Outdated Show resolved Hide resolved
// Wait until Kroma MPT migration completed when it's set
if cfg.DeployConfig.L2GenesisKromaMPTTimeOffset != nil {
mptTimeOffset := *cfg.DeployConfig.L2GenesisKromaMPTTimeOffset
mptMigrationNextBlock := uint64(mptTimeOffset)/cfg.DeployConfig.L2BlockTime + 1
Copy link
Contributor

Choose a reason for hiding this comment

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

Since the transition is applied from mptMigrationBlock, wouldn't it be more accurate to test by MPT block instead of next?

Copy link
Contributor

@kangsorang kangsorang left a comment

Choose a reason for hiding this comment

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

LGTM

@seolaoh seolaoh force-pushed the test/distribute-fee-mpt branch from 347670f to e610b40 Compare December 17, 2024 09:59
Base automatically changed from feat/add-op-l1block to feat/zkvm-fault-proof December 18, 2024 05:55
@Pangssu Pangssu requested a review from a team as a code owner December 18, 2024 05:55
@Pangssu Pangssu removed the request for review from a team December 18, 2024 06:13
@Pangssu
Copy link
Contributor

Pangssu commented Dec 18, 2024

Could you rebase please?

@seolaoh seolaoh force-pushed the test/distribute-fee-mpt branch 2 times, most recently from 85f4990 to 839536f Compare December 18, 2024 09:01
@seolaoh seolaoh changed the base branch from feat/zkvm-fault-proof to feat/delay-engine-call December 18, 2024 09:02
@Pangssu Pangssu force-pushed the feat/delay-engine-call branch 2 times, most recently from 8b125c0 to 863d987 Compare December 19, 2024 05:00
Base automatically changed from feat/delay-engine-call to feat/zkvm-fault-proof December 19, 2024 05:05
@seolaoh seolaoh force-pushed the test/distribute-fee-mpt branch from 839536f to 553f007 Compare December 19, 2024 05:05
@seolaoh seolaoh merged commit 7ed0bac into feat/zkvm-fault-proof Dec 19, 2024
3 checks passed
@seolaoh seolaoh deleted the test/distribute-fee-mpt branch December 19, 2024 06:37
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.

4 participants