bug-findutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #57839] Remove/fix getdtablesize tests


From: Bernhard Voelker
Subject: [bug #57839] Remove/fix getdtablesize tests
Date: Wed, 19 Feb 2020 16:58:23 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Update of bug #57839 (project findutils):

                  Status:               Need Info => Works For Me           
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

Thanks for adding more information.

I'm still quite confused about that combination.
I used the mentioned centos:6 in a docker container, and therefore I had
glibc-2.12 (from the container's Centos 6 system), and kernel 5.5.1 from
my host OS openSUSE:Tumbleweed.
Therefore I wonder how you could have a newer glibc-2.30 on Centos 6.

Anyway:

> failures occur only when building against a recent (2.30) glibc on older
(2.6.x) kernels.

As can be seen from the output you provided, both failures originate
from dup2 not working on that combination.

Therefore, this is not a test framework failure aka false positive,
but a real issue on a system with that - highly unlikely - combination
of glibc-2.30 and kernel-2.6.x.  To be honest, I would expect more fallout
from such a combination.

Therefore, I would not want to mask that gnulib test in upstream GNU
findutils,
because it is useful in general, but I'd rather suggest that you keep your
patch downstream to skip that test in your environment.
It is not uncommon to skip some tests which are known to fail in specialized
build environments (if one can rule out that this won't happen on a real
system).

I'll therefore closing this issue as "Works For Me", but the discussion
can of course continue (and once there would be proof that this is a test
failure
that has to be dealt with, the issue could be reopened).

Thanks for reporting this issue.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57839>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]