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

feat: use new engine in e2e tests for OP #13558

Merged
merged 1 commit into from
Dec 27, 2024
Merged

feat: use new engine in e2e tests for OP #13558

merged 1 commit into from
Dec 27, 2024

Conversation

klkvr
Copy link
Collaborator

@klkvr klkvr commented Dec 25, 2024

Defaults to new engine when running op e2e tests.

This required some changes to a test

@@ -43,13 +43,19 @@ async fn can_sync() -> eyre::Result<()> {
.update_optimistic_forkchoice(canonical_chain[tip_index - reorg_depth])
.await?;
second_node
.wait_block((tip - reorg_depth) as u64, canonical_chain[tip_index - reorg_depth], true)
.wait_block((tip - reorg_depth) as u64, canonical_chain[tip_index - reorg_depth], false)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this marks whether we need to wait for Finish stage to advance which might not happen if persistence threshold is not reached

.await?;
second_node.engine_api.canonical_stream.next().await.unwrap();

// On third node, sync optimistically up to block number 90a
// Trigger backfil sync until block 80
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This seems to be an edge case for new engine. If we sync to the tip via backfill sync and then a reorg happens, we're not going to be able to process it because we will be missing trie updates in in-memory state.

I guess this is unlikely because we'd mostly use backfill sync to reach finalized block

Copy link

codspeed-hq bot commented Dec 25, 2024

CodSpeed Performance Report

Merging #13558 will degrade performances by 10.37%

Comparing klkvr/op-e2e-engine (2c82290) with main (951e2fd)

Summary

❌ 1 regressions
✅ 76 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark main klkvr/op-e2e-engine Change
`prefix set size: 10 BTreeSet with Iterator:any lookup` 4.9 µs

@klkvr klkvr added this pull request to the merge queue Dec 27, 2024
Merged via the queue into main with commit 6049b6e Dec 27, 2024
43 of 44 checks passed
@klkvr klkvr deleted the klkvr/op-e2e-engine branch December 27, 2024 11:15
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