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

Test suite is too slow #981

Closed
freesig opened this issue Feb 3, 2023 · 3 comments
Closed

Test suite is too slow #981

freesig opened this issue Feb 3, 2023 · 3 comments
Assignees
Labels
architecture Something related to the architecture or the architecture description itself. ci The issue related to CI fuel-core tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable.

Comments

@freesig
Copy link
Contributor

freesig commented Feb 3, 2023

Our full test sweet is taking too long to run. Especially the p2p tests. This slows down our development cycle and leads to avoiding running the entire suite.

@freesig freesig added tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable. fuel-core architecture Something related to the architecture or the architecture description itself. labels Feb 3, 2023
@Voxelot
Copy link
Member

Voxelot commented Feb 6, 2023

Using cargo nextest our suite only takes 19s on my ryzen 5950x

@freesig
Copy link
Contributor Author

freesig commented Feb 6, 2023

Is that with the p2p feature also this isn't really a solution. Our test suite is slow because of the timing of the p2p tests which can be lowered for testing instead of just relying on running in on multiple threads. For example the CI currently takes 14 mins to run just the cargo test.

@xgreenx xgreenx added the ci The issue related to CI label May 12, 2023
@xgreenx xgreenx self-assigned this Aug 7, 2023
@xgreenx
Copy link
Collaborator

xgreenx commented Aug 24, 2023

We run tests very fast after #1231. But we still spend a lot of time building tests per crate #987. But it is a problem during the first build without a cache, so doesn't hurt too much for follow-up commits.

I close this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Something related to the architecture or the architecture description itself. ci The issue related to CI fuel-core tech-debt The issue is to improve the current code and make it more clear/generic/reusable/pretty/avoidable.
Projects
None yet
Development

No branches or pull requests

3 participants