From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] more parallelization fixes
Date: Tue, 13 Aug 2013 21:03:00 -0000 [thread overview]
Message-ID: <1376427803-16608-1-git-send-email-tromey@redhat.com> (raw)
This series updates more parts of the test suite to be parallel-safe.
I think the patches are all reasonably straightforward.
After this series, we still aren't really done, but we're much closer
to the end. I think there will be one more series like this one --
just updates to various tests -- and then the final patches to modify
the Makefiles and switch "make -jN check" to the new scheme. At that
point I'll also dig up my notes and (re-)post some information about
how well the test suite scales.
Tom
next reply other threads:[~2013-08-13 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 21:03 Tom Tromey [this message]
2013-08-13 21:03 ` [PATCH 5/5] fix gdb.arch to be parallel-safe Tom Tromey
2013-08-14 8:33 ` Pedro Alves
2013-08-14 17:12 ` Tom Tromey
2013-08-13 21:03 ` [PATCH 4/5] fix gdb.python " Tom Tromey
2013-08-14 8:33 ` Pedro Alves
2013-08-14 16:20 ` Tom Tromey
2013-08-13 21:03 ` [PATCH 3/5] use standard_temp_file in another caching proc Tom Tromey
2013-08-13 21:03 ` [PATCH 2/5] introduce gdb_remote_download and finish parallel fixes in gdb.dwarf2 Tom Tromey
2013-08-26 2:20 ` Yao Qi
2013-08-26 15:54 ` Tom Tromey
2013-08-27 0:20 ` Yao Qi
2013-08-13 21:03 ` [PATCH 1/5] fix some gdb.dwarf2 tests for parallel safety Tom Tromey
2013-08-27 15:16 ` Testsuite regression for fission + gdbindex run [Re: [PATCH 1/5] fix some gdb.dwarf2 tests for parallel safety] Jan Kratochvil
2013-08-14 8:34 ` [PATCH 0/5] more parallelization fixes Pedro Alves
2013-08-22 13:34 ` Tom Tromey
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=1376427803-16608-1-git-send-email-tromey@redhat.com \
--to=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).