From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add more parallelization to gdb.base testing
Date: Fri, 22 Jun 2012 16:20:00 -0000 [thread overview]
Message-ID: <87a9zviajo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120618163310.98BF71E136F@ruffy2.mtv.corp.google.com> (Doug Evans's message of "Mon, 18 Jun 2012 09:33:10 -0700 (PDT)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> This patch speeds up gdb testing at -j6 on my machine from 7mins
Doug> to 4mins. I didn't want to get too carried away here, this felt
Doug> like a good compromise. I split the range into four roughly equal
Doug> partitions alphabet wise, then noticed that [a-g] has far more
Doug> files than the others so made the split more refined. I'm happy
Doug> to use whatever partitioning folks want, I just want the 4mins (or
Doug> better).
Doug> Ok to check in?
We discussed this on irc a bit, but for the record, I think there are
latent bugs that this patch will expose.
For example, several tests in gdb.base use the same executable name:
barimba. egrep 'set testfile.* "break"$' *.exp
completion.exp:set testfile "break"
condbreak.exp:set testfile "break"
define.exp:set testfile "break"
ena-dis-br.exp:set testfile "break"
environ.exp:set testfile "break"
info-proc.exp:set testfile "break"
maint.exp:set testfile "break"
Jan went through and fixed bugs like this for the current split.
Tom
next prev parent reply other threads:[~2012-06-22 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 16:33 Doug Evans
2012-06-18 16:48 ` Joel Brobecker
2012-06-22 16:20 ` Tom Tromey [this message]
2012-06-18 16:35 Doug Evans
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=87a9zviajo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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