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

chore: fix flakey e2e fees failures test #8807

Merged
merged 3 commits into from
Sep 26, 2024
Merged

Conversation

just-mitch
Copy link
Contributor

@just-mitch just-mitch commented Sep 25, 2024

If the proven chain weren't caught up before we took the measurement for coinbase's L1 balance, it could look as though the wrong amount of fees were paid out.

@just-mitch just-mitch changed the title chore: set max block size in fees test chore: fix flakey e2e fees failures test Sep 26, 2024
@ludamad ludamad added the e2e-fees-failure CI: Enables this CI job. label Sep 26, 2024
@ludamad ludamad enabled auto-merge (squash) September 26, 2024 02:58
@ludamad ludamad merged commit 99bac95 into master Sep 26, 2024
101 checks passed
@ludamad ludamad deleted the mt/8783-fix-fees-test branch September 26, 2024 03:02
Rumata888 pushed a commit that referenced this pull request Sep 27, 2024
If the proven chain weren't caught up before we took the measurement for
coinbase's L1 balance, it could look as though the wrong amount of fees
were paid out.
Rumata888 pushed a commit that referenced this pull request Sep 27, 2024
If the proven chain weren't caught up before we took the measurement for
coinbase's L1 balance, it could look as though the wrong amount of fees
were paid out.
Rumata888 pushed a commit that referenced this pull request Sep 27, 2024
If the proven chain weren't caught up before we took the measurement for
coinbase's L1 balance, it could look as though the wrong amount of fees
were paid out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e-fees-failure CI: Enables this CI job.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants