-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[forge] Split out test suites from main #15033
Conversation
⏱️ 1h 32m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
237fba6
to
339f2cd
Compare
This comment has been minimized.
This comment has been minimized.
339f2cd
to
2e80bb3
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There are a lot of tests and cruft in with the main forge cli Split them out into suites Test Plan: running forge on PR succeeds
2e80bb3
to
5b2c544
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
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.
LGTM
@@ -617,7 +518,7 @@ fn get_test_suite( | |||
|
|||
// Otherwise, check the test name against the grouped test suites | |||
if let Some(test_suite) = get_land_blocking_test(test_name, duration, test_cmd) { | |||
return Ok(test_suite); | |||
Ok(test_suite) |
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.
Should we also remove the return statements from the other branches to match 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.
Woops yeah i already fixed this in another commit forgot to pick
// SPDX-License-Identifier: Apache-2.0 | ||
|
||
pub mod dag; | ||
pub mod db; |
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.
Probably for a future PR. Now that we have the test suites split up into different modules, it'd be great to have module-level docs for what each test suite is doing. @igor-aptos added some comments for forge-stable in #14775 , maybe we should move some of the docs to these files?
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 in general i think these should live with the tests themselves not in docs on a forge workflow
There are a lot of tests and cruft in with the main forge cli
Split them out into suites
Test Plan:
running forge on PR succeeds