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

Doc: Workaround for Running cargo test locally without signficant memory #9402

Merged
merged 2 commits into from
Feb 29, 2024

Conversation

devinjdangelo
Copy link
Contributor

Which issue does this PR close?

Closes #9398
Closes #5347

Rationale for this change

New contributors (myself included!) often run cargo test locally when setting up DataFusion for development and are surprised to see their system lock up or fail to complete the tests. This is due to very high memory requirements to complete the tests with default parallelism. See linked issues for more discussion on the cause of high memory usage.

What changes are included in this PR?

Documents this phenomenon in the contributors documentation page and suggests a workaround to run

cargo test -- --test-threads 1

if you run into memory limitations.

Are these changes tested?

No - just a doc update.

Are there any user-facing changes?

New contributor docs

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

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

Thank you @devinjdangelo

@comphead comphead merged commit a8a3c5d into apache:main Feb 29, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants