Bug 106133 - make check "OSError: [Errno 24] Too many open files"
Summary: make check "OSError: [Errno 24] Too many open files"
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Dylan Baker
QA Contact: mesa-dev
Depends on:
Reported: 2018-04-19 07:16 UTC by Vinson Lee
Modified: 2018-04-23 16:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Vinson Lee 2018-04-19 07:16:01 UTC
make check fails glsl/glcpp/tests/glcpp-test-cr-lf.sh test.

$ ./glsl/glcpp/tests/glcpp_test.py ./glsl/glcpp/glcpp glsl/glcpp/tests --windows --oldmac
  File "./glsl/glcpp/tests/glcpp_test.py", line 221, in <module>
  File "./glsl/glcpp/tests/glcpp_test.py", line 211, in main
    success = success and test_oldmac(args)
  File "./glsl/glcpp/tests/glcpp_test.py", line 169, in test_oldmac
    return _replace_test(args, '\r')
  File "./glsl/glcpp/tests/glcpp_test.py", line 144, in _replace_test
    args.glcpp, tmpfile, testfile + '.expected', nl_format=replace)
  File "./glsl/glcpp/tests/glcpp_test.py", line 65, in test_output
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1223, in _execute_child
    errpipe_read, errpipe_write = self.pipe_cloexec()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1175, in pipe_cloexec
    r, w = os.pipe()
OSError: [Errno 24] Too many open files
Comment 1 Dylan Baker 2018-04-19 16:35:07 UTC
I'll look into this and see what I can do. I have an idea of how I might fix it, but I'll have to see if I can reproduce this on my mac.
Comment 2 Dylan Baker 2018-04-23 16:56:13 UTC
0e945fdf23b..dbf5b772b3b  master -> master

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.