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.

Sign up for GitHub

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

Jump to bottom

[Feature Request] Provide the minimal disk space requirement for CMake testing. #2066

Open
hyoklee opened this issue Aug 24, 2022 · 2 comments
Open

[Feature Request] Provide the minimal disk space requirement for CMake testing. #2066

hyoklee opened this issue Aug 24, 2022 · 2 comments
Assignees
@bmribler
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 3. Low 🔽 Code cleanup, small feature change requests, etc. Type - Improvement Improvements that don't add a new feature or functionality

Comments

@hyoklee
Copy link
Member

hyoklee commented Aug 24, 2022

Is your feature request related to a problem? Please describe.
make test failed when the available storage is 1.6G.

Describe the solution you'd like
Provide a documentation on how much space is required.

Describe alternatives you've considered
It would be nice if 'make test' can skip some tests if they require space beyond what's available.

Additional context
I think this will be useful for small VMs and embedded system.
@hyoklee
Copy link
Member Author

hyoklee commented Aug 26, 2022

It seems that 4G is required.

@derobins derobins added Priority - 3. Low 🔽 Code cleanup, small feature change requests, etc. Component - Testing Code in test or testpar directories, GitHub workflows Type - Improvement Improvements that don't add a new feature or functionality labels May 4, 2023
@derobins
Copy link
Member

derobins commented May 4, 2023

The amount of disk space used is because CMake creates statically linked test programs. CMake should not do this when we're also building the shared library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bmribler bmribler

Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 3. Low 🔽 Code cleanup, small feature change requests, etc. Type - Improvement Improvements that don't add a new feature or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@derobins @hyoklee @bmribler