Skip to content

ci(l1): Updated CI to include spamoor and new version of ethereum-package #2627

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

Merged
merged 17 commits into from
Jun 11, 2025

Conversation

fedacking
Copy link
Contributor

Motivation

We are updating the kurtosis ethereum package to include spamoor. I'm using this pr to test the CI changes.

Description

  • Changes ethereum package version.
  • Adds spamoor to tx_networ_param

Closes #2480

@fedacking fedacking changed the title Modified assertoor to use updated branch ci(l1): Updated CI to include spamoor and new version of ethereum-package Apr 28, 2025
@fedacking fedacking marked this pull request as ready for review April 28, 2025 20:48
@fedacking fedacking requested a review from a team as a code owner April 28, 2025 20:48
@@ -12,6 +12,13 @@ participants:
additional_services:
- assertoor
- dora
- spamoor

spamoor_params:
Copy link
Collaborator

Choose a reason for hiding this comment

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

what about the tx spammer?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Assertoor generates the transactions for this test. Spamoor sends blob transactions to add stress.

@fedacking
Copy link
Contributor Author

CI is flaky until #2682 is resolved. Shouldn't be merged untils it's fixed and retested.

@fedacking fedacking marked this pull request as ready for review May 29, 2025 22:19
spammers:
- scenario: blobs
config:
# The eip limits our blob transactions to 6 per block, we keep it slightly under that.
Copy link
Collaborator

Choose a reason for hiding this comment

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

why?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought it had issues with that number. That was incorrect, it works with 6. Fixing comment.

Copy link
Collaborator

@rodrigo-o rodrigo-o left a comment

Choose a reason for hiding this comment

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

🚀

@fedacking fedacking added this pull request to the merge queue Jun 11, 2025
Merged via the queue into main with commit 69e5116 Jun 11, 2025
20 checks passed
@fedacking fedacking deleted the feat/add-spamoor branch June 11, 2025 17:47
rodrigo-o pushed a commit that referenced this pull request Jun 11, 2025
…kage (#2627)

**Motivation**

We are updating the kurtosis ethereum package to include spamoor. I'm
using this pr to test the CI changes.

**Description**

- Changes ethereum package version.
- Adds spamoor to tx_networ_param

Closes #2480

---------

Co-authored-by: Tomás Grüner <47506558+MegaRedHand@users.noreply.github.com>
pedrobergamini pushed a commit to pedrobergamini/ethrex that referenced this pull request Aug 24, 2025
…kage (lambdaclass#2627)

**Motivation**

We are updating the kurtosis ethereum package to include spamoor. I'm
using this pr to test the CI changes.

**Description**

- Changes ethereum package version.
- Adds spamoor to tx_networ_param

Closes lambdaclass#2480

---------

Co-authored-by: Tomás Grüner <47506558+MegaRedHand@users.noreply.github.com>
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.

Update Spamoor to new configuration
4 participants