public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Jakub Jelinek <jakub@redhat.com>, Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org
Subject: Fwd: runtest takes too long on get_local_hostname
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <401e88ea-151e-3b76-4077-0a6e7a029806@suse.de> (raw)
In-Reply-To: <abfcef90-6746-63be-301d-35825553f783@suse.de>

Hi,

FYI, I ran into this dejagnu problem with the dwz testsuite.

Filed as http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35069 .

Thanks,
- Tom

-------- Forwarded Message --------
Subject: runtest takes too long on get_local_hostname
Date: Mon, 1 Apr 2019 12:05:50 +0200
From: Tom de Vries <tdevries@suse.de>
To: bug-dejagnu@gnu.org

Hi,

I've setup a dejagnu testsuite for the dwz component (
https://sourceware.org/git/?p=dwz.git;a=summary ).

I'm running into the following problem.

Usually the testsuite runs in 12 seconds, but sometimes it takes more
than a minute (I managed to reproduce the same problem by running a
single gcc testsuite test-case).

I tracked this down to tcl info hostname taking a long time, when:
- having a vpn session active, and
- having no network connection

I manage to work around this by editing /usr/share/dejagnu/runtest.exp
and redefining get_local_hostname like this:
...
proc get_local_hostname { } {
    return [exec hostname]
}
...

I think it's a bug that a testsuite run that tests no network
functionality slows down by a factor of 5 when there's no network
connection.

[ In absence of a fix, I would already be grateful if somebody can point
out to me how I can work around this in a site.exp or board file or some
such, I tried myself but didn't manage to make that work. ]

Thanks,
- Tom

           reply	other threads:[~2019-04-01 10:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <abfcef90-6746-63be-301d-35825553f783@suse.de>]

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=401e88ea-151e-3b76-4077-0a6e7a029806@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=mark@klomp.org \
    /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).