-
Notifications
You must be signed in to change notification settings - Fork 46
feat: replace legacy replays with PRAGUE replays
#2461
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: replace legacy replays with PRAGUE replays
#2461
Conversation
ab4b4bc to
4980ed8
Compare
b9e0d78 to
9ac5a84
Compare
493f317 to
1e7585b
Compare
5b18233 to
8d536d4
Compare
This refactors the existing legacy replay tests, such they are: (1) all disabled; (2) live in their own package to avoid clutter; (3) all the actual replays have been moved into their own folder as well.
The goal here is simply to figure out what the batch size is for the various testing regimes (fast replay, nightly, weekly).
This simplifies the way the existing gradle test tasks are written, and also adds a notion of "weekly replay tests".
8d536d4 to
c91055e
Compare
arithmetization/src/test/java/net/consensys/linea/pragueReplayTests/Issue1335Tests.java
Show resolved
Hide resolved
| @@ -376,6 +282,12 @@ tasks.register("jacocoPrcCallTestsReport", JacocoReport) { | |||
| executionData(prcCallTests) | |||
| } | |||
|
|
|||
| jacocoTestReport { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the most generic one, could go at the beginning but we can merge like this :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I wasn't really sure what to do with the jacoco tasks. For example, whether they could be simplified, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really, because when I want to aggregate them all to have coverage, if they have the same name I'm not able to. You did right just to move them around 👍
| @@ -71,7 +71,33 @@ tasks.withType(Test).configureEach { | |||
| systemProperty name, System.getProperty(name) | |||
| } | |||
| } | |||
|
|
|||
| // Configure default parallelism | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good cleaning / reorganizing of this file !! Thank you !
|
Thank you @DavePearce for capturing all these replays - this is a very important PR !! |
|
One note : we will be able to unpin the nightly replays from the GA when we see it |
Note
Switches replay tests to Prague datasets (new suites), relegates legacy replays under legacy/, and updates Gradle/CI to use a unified JUNIT_TESTS_PARALLELISM and consolidated workflows.
pragueReplayTests: Fast, Nightly, Weekly, Sepolia) usingMAINNET_TESTCONFIG(PRAGUE)andreplays/prague/*inputs.legacyReplaytests, prefix inputs withlegacy/, and disable many legacy tests.ReplayTestToolstonet.consensys.lineaand update imports; enable Prague coinbase handling viaFork.isPostPrague.JUNIT_TESTS_PARALLELISM; remove task-specific*_PARALLELISMenvs.JUNIT_TESTS_PARALLELISMacross jobs.JUNIT_TESTS_PARALLELISM..github/workflows/gradle-nightly-replay-tests.yml.Written by Cursor Bugbot for commit c91055e. This will update automatically on new commits. Configure here.