From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Bernd Schmidt <bernds@codesourcery.com>,
Andrew MacLeod <amacleod@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: parallel check output changes?
Date: Fri, 19 Sep 2014 09:37:00 -0000 [thread overview]
Message-ID: <20140919093723.GA26414@gate.crashing.org> (raw)
In-Reply-To: <20140918184455.GB28595@gate.crashing.org>
On Thu, Sep 18, 2014 at 01:44:55PM -0500, Segher Boessenkool wrote:
> I am testing a patch that is just
>
>
> diff --git a/contrib/dg-extract-results.py b/contrib/dg-extract-results.py
> index cccbfd3..3781423 100644
> --- a/contrib/dg-extract-results.py
> +++ b/contrib/dg-extract-results.py
> @@ -117,7 +117,7 @@ class Prog:
> self.tool_re = re.compile (r'^\t\t=== (.*) tests ===$')
> self.result_re = re.compile (r'^(PASS|XPASS|FAIL|XFAIL|UNRESOLVED'
> r'|WARNING|ERROR|UNSUPPORTED|UNTESTED'
> - r'|KFAIL):\s*(\S+)')
> + r'|KFAIL):\s*(.+)')
> self.completed_re = re.compile (r'.* completed at (.*)')
> # Pieces of text to write at the head of the output.
> # start_line is a pair in which the first element is a datetime
Tested that with four runs on powerpc64-linux, four configs each time;
test-summary
shows the same in all cases. Many lines have moved compared to without
the patch, but that cannot be helped. Okay for mainline?
2014-09-19 Segher Boessenkool <segher@kernel.crashing.org>
contrib/
* dg-extract-results.py (Prog.result_re): Include options in test name.
> Relatedly, is it just me or are most lines of the test summaries (the "#"
> lines after "===") missing since the parallelisation patches?
This is still open.
I also did some timings for make -j60 -k check, same -m64,-m32,-m32/-mpowerpc64,
-m64/-mlra configs. A run takes 65m, is effectively 42x parallel, and has 15%
system time.
Segher
next prev parent reply other threads:[~2014-09-19 9:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 12:56 Andrew MacLeod
2014-09-18 13:08 ` Jakub Jelinek
2014-09-18 13:05 ` Andrew MacLeod
2014-09-18 15:45 ` Andrew MacLeod
2014-09-18 17:33 ` Bernd Schmidt
2014-09-18 17:36 ` Jakub Jelinek
2014-09-18 18:45 ` Segher Boessenkool
2014-09-19 9:37 ` Segher Boessenkool [this message]
2014-09-19 16:32 ` Mike Stump
2014-09-23 15:33 ` Richard Sandiford
2014-09-23 15:43 ` Jakub Jelinek
2014-09-24 14:55 ` Andrew MacLeod
2014-09-24 16:11 ` Segher Boessenkool
2014-09-24 16:29 ` Andrew MacLeod
2014-09-24 17:59 ` Andrew MacLeod
2014-09-25 12:22 ` Andrew MacLeod
2014-09-25 17:02 ` Segher Boessenkool
2014-10-02 16:47 ` Segher Boessenkool
2014-10-02 17:05 ` Jakub Jelinek
2014-10-02 17:46 ` Richard Sandiford
2014-10-02 18:00 ` Jakub Jelinek
2014-10-04 10:32 ` Richard Sandiford
2014-10-05 17:53 ` Mike Stump
2014-10-02 18:15 ` Segher Boessenkool
2014-10-02 19:05 ` Andrew MacLeod
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=20140919093723.GA26414@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amacleod@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).