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

No space left on device errors #1759

Closed
htuch opened this issue Aug 24, 2018 · 2 comments
Closed

No space left on device errors #1759

htuch opened this issue Aug 24, 2018 · 2 comments

Comments

@htuch
Copy link
Contributor

htuch commented Aug 24, 2018

From https://oss-fuzz.com/v2/testcase-detail/5644730562510848:

[2018-08-23 21:05:44.628][22433][critical][assert] test/test_common/environment.cc:54] assert failure: ::mkdtemp(test_tmpdir) != nullptr. Details: Failed to create tmpdir /tmp/envoy_test_tmp.LBSV5i No space left on device

Thoughts on how we can be hitting this in ClusterFuzz? We started to run into issues like this after recently switching to using mkdtemp to attempt to give each fuzz test its own area of the filesystem, to reduce the chance of interactions between independent test cases.

@Dor1s
Copy link
Contributor

Dor1s commented Aug 24, 2018

Do you remove those dirs afterwards?

@htuch
Copy link
Contributor Author

htuch commented Aug 27, 2018

Yep, I had thought the artifacts would be small enough, but I guess they add up. Should be fixed by envoyproxy/envoy#4253.

@htuch htuch closed this as completed Aug 27, 2018
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