Description of problem: PR binutils/23460 testcase from ld internal testsuite fails on RHEL-9.0.0-20210617.1: (...) spawn [open ...] PASS: Build pr23460*.o sh -c "ulimit -n 16; /root/rpmbuild/BUILD/binutils-2.35.2/ld/../binutils/ar -rc --plugin /usr/libexec/gcc/x86_64-redhat-linux/11/liblto_plugin.so tmpdir/libpr23460.a tmpdir/pr23460a.o tmpdir/pr23460b.o tmpdir/pr23460c.o tmpdir/pr23460d.o tmpdir/pr23460e.o tmpdir/pr23460f.o" Executing on host: sh -c {sh -c "ulimit -n 16; /root/rpmbuild/BUILD/binutils-2.35.2/ld/../binutils/ar -rc --plugin /usr/libexec/gcc/x86_64-redhat-linux/11/liblto_plugin.so tmpdir/libpr23460.a tmpdir/pr23460a.o tmpdir/pr23460b.o tmpdir/pr23460c.o tmpdir/pr23460d.o tmpdir/pr23460e.o tmpdir/pr23460f.o" 2>&1} /dev/null ld.tmp (timeout = 300) spawn [open ...] /root/rpmbuild/BUILD/binutils-2.35.2/binutils/.libs/lt-ar: tmpdir/pr23460e.o: Too many open files /root/rpmbuild/BUILD/binutils-2.35.2/binutils/.libs/lt-ar: tmpdir/pr23460e.o: Too many open files FAIL: PR binutils/23460 (...) === ld Summary === # of expected passes> > 2541 # of unexpected failures> 1 # of expected failures> > 57 # of unresolved testcases> 4 # of untested testcases>> 1 # of unsupported tests> > 23 ./ld-new 2.35.2-5.el9 This issue is currently reproducible on all supported architectures. Version-Release number of selected component (if applicable): binutils-2.35.2-5.el9 gcc-11.0.1-0.3.1.el9 RHEL-9.0.0-20210617.1 kernel 5.13.0-0.rc4.33.el9 How reproducible: 100% Steps to Reproduce: 1. yum-builddep -y binutils-2.35.2-5.el9.src.rpm 2. rpm -ivh binutils-2.35.2-5.el9.src.rpm 3. rpmbuild -bc /root/rpmbuild/SPECS/binutils.spec
(In reply to Edjunior Barbosa Machado from comment #0) > /root/rpmbuild/BUILD/binutils-2.35.2/binutils/.libs/lt-ar: > tmpdir/pr23460e.o: Too many open files > FAIL: PR binutils/23460 I cannot reproduce this failure. :-( For example, this scratch build shows PR 23640 PASSing and in fact no linker testsuite failures at all: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37625537 The failure is strange. The error message indicates that all the available file descriptors have been used up, and the fact that the test is being run with "ulimit -n 16" suggests that it is checking to make sure that the lto plugin can work in an environment with a restricted number of descriptors. Is it possible that you are running the test in an environment with a very very restricted number of file descriptors available ? (The manual page for ulimit does say that the -n option does not always have an affect). Are you able to run the test by hand ? If so, can you run it with "strace" as a prefix so that we can see how many files are opened ?
I have not had any response to my enquiries so I think that the simplest thing to do is to close this BZ and reopen it if the issue ever arises again.