public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thkala at softlab dot ece dot ntua dot gr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5204] New: The glibc-2.7 sha512c-test fails with a timeout - needs an increased wait time
Date: Sun, 21 Oct 2007 21:23:00 -0000	[thread overview]
Message-ID: <20071021212338.5204.thkala@softlab.ece.ntua.gr> (raw)

Hi,

As per the subject, the sha512c test of glibc-2.7 fails on my system:

GCONV_PATH=/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/iconvdata LC_ALL=C
  /usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/elf/ld-linux.so.2
--library-path
/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/math:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/elf:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/dlfcn:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/nss:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/nis:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/rt:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/resolv:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/crypt:/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/nptl
/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/crypt/sha512c-test  >
/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/crypt/sha512c-test.out
Timed out: killed the child process
make[2]: ***
[/usr/src/rpm/BUILD/glibc-2.7/glibc-2.7-1mp-objdir/crypt/sha512c-test.out] Error 1

Apparently the default timeout of 2 seconds that this test uses is not enough,
since setting the TIMEOUTFACTOR environment variable to 2 (i.e. a timeout of 4
sec) allows the test to complete without errors.

My system is an Intel Pentium-M (Centrino) 1.7GHz, and the same error has been
verified by another person (wolfpac from the #lfs-support IRC channel) with a
Pentium-4 1.8 GHz.

OS: linux-2.6.22
Kernel headers used: linux-2.6.22.10
CC: gcc-4.2.2 + binutils-2.18
CFLAGS:-O2 -pipe -march=pentium-m

I am filing this as a bug, because I think both machines are recent and fast
enough to not have a test fail for that reason, unless of course something more
subtle/sinister is happening, and the test was really supposed to finish in 2
seconds...

Regards,

Theodoros V. Kalamatianos

-- 
           Summary: The glibc-2.7 sha512c-test fails with a timeout - needs
                    an increased wait time
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: thkala at softlab dot ece dot ntua dot gr
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-mandriva-linux-gnu
  GCC host triplet: i686-mandriva-linux-gnu
GCC target triplet: i686-mandriva-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=5204

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-10-21 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21 21:23 thkala at softlab dot ece dot ntua dot gr [this message]
2007-10-27 15:26 ` [Bug libc/5204] " aj at suse dot de
2007-10-28 18:38 ` thkala at softlab dot ece dot ntua dot gr
2007-10-28 19:47 ` drepper at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071021212338.5204.thkala@softlab.ece.ntua.gr \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).