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

make test: ERROR: mmap shmem buffer: No space left on device #1865

Open
vt-alt opened this issue Dec 23, 2023 · 2 comments
Open

make test: ERROR: mmap shmem buffer: No space left on device #1865

vt-alt opened this issue Dec 23, 2023 · 2 comments

Comments

@vt-alt
Copy link

vt-alt commented Dec 23, 2023

I thought we would run tests when building a package (for ALT Linux). But frequently runtest fails with a lot of messages like this (on aarch64 and x86_64):

 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer
 ERROR: mmap shmem buffer: No space left on device
mcount: /usr/src/RPM/BUILD/uftrace-0.14/libmcount/record.c:81:prepare_shmem_buffer

uftrace version: v0.14-88-gad862218. Tests are run under user without setting perf_event_paranoid=1 and kptr_restrict=0. Tests are run with make -j$(nproc) (-j32), and there a lot of space on /tmp (64G).

Maybe some tests could be skipped to make them more robust? (And tests faster.)

@namhyung
Copy link
Owner

Thanks for the report. Maybe there are cases it didn't clean up all the resourses when the test failed. I need to investigate it more.

But for faster and more robust test, you can enable subset of tests with TESTARG argument on the make. For now, I think you can run like this.

$ make -j32 runtest TESTARG=basic

@vt-alt
Copy link
Author

vt-alt commented Dec 25, 2023

Thinks for suggestion, I will use it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants