From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jkratoch@redhat.com>
Subject: Re: RFC: parallelize "make check"
Date: Mon, 29 Jun 2009 18:05:00 -0000 [thread overview]
Message-ID: <m3ab3qapbd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090629165708.GA30963@caradoc.them.org> (Daniel Jacobowitz's message of "Mon\, 29 Jun 2009 12\:57\:08 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Tom> Just FYI, Jan mentioned on irc that this made some existing test suite
Tom> instability worse.
Daniel> I've been having a lot of trouble with foll-fork.exp printing output
Daniel> after prompts.
I hadn't heard about that one... Jan?
What he did mention to me is:
gdb.mi/mi-file-transfer.exp, gdb.server/file-transfer.exp,
gdb.base/focus-cmd-prev.exp, gdb.xml/tdesc-regs.exp,
gdb.base/watchpoint.exp and some others already filtered out randomly
FAIL when run in parallel
Tom
next prev parent reply other threads:[~2009-06-29 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 19:27 Tom Tromey
2009-06-25 3:15 ` Eli Zaretskii
2009-06-25 20:21 ` Tom Tromey
2009-06-26 6:53 ` Eli Zaretskii
2009-06-26 15:56 ` Tom Tromey
2009-06-27 9:13 ` Eli Zaretskii
2009-06-25 14:55 ` Joel Brobecker
2009-06-25 15:09 ` Tom Tromey
2009-06-25 22:58 ` Pedro Alves
2009-06-26 1:34 ` Daniel Jacobowitz
2009-06-26 17:45 ` Tom Tromey
2009-06-26 20:27 ` Joseph S. Myers
2009-06-26 23:41 ` Joel Brobecker
2009-06-29 16:43 ` Tom Tromey
2009-06-29 16:57 ` Daniel Jacobowitz
2009-06-29 18:05 ` Tom Tromey [this message]
2009-06-29 18:38 ` Daniel Jacobowitz
2009-06-29 21:17 ` Jan Kratochvil
2009-07-01 12:06 ` [patch] testsuite: Fix multiple runs in parallel on a single host [Re: RFC: parallelize "make check"] Jan Kratochvil
2009-07-06 18:39 ` Tom Tromey
2009-07-06 18:53 ` [patch] testsuite: Fix multiple runs in parallel on a single host Jan Kratochvil
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=m3ab3qapbd.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jkratoch@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