From: Andrew MacLeod <amacleod@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Jakub Jelinek <jakub@redhat.com>,
Bernd Schmidt <bernds@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
richard.sandiford@arm.com, rdsandiford@googlemail.com
Subject: Re: parallel check output changes?
Date: Thu, 02 Oct 2014 19:05:00 -0000 [thread overview]
Message-ID: <542DA1C3.7070607@redhat.com> (raw)
In-Reply-To: <20141002181450.GB25260@gate.crashing.org>
On 10/02/2014 02:14 PM, Segher Boessenkool wrote:
> On Thu, Oct 02, 2014 at 06:46:19PM +0100, Richard Sandiford wrote:
>> Segher Boessenkool <segher@kernel.crashing.org> writes:
>>> On Wed, Sep 24, 2014 at 10:54:57AM -0400, Andrew MacLeod wrote:
>>>> Is this suppose to be resolved now? I'm still seeing some issues with a
>>>> branch cut from mainline from yesterday.
>>> Confirmed. The following patch works for me, and Andrew has tested it
>>> as well. The comment it removes isn't valid before the patch either.
>> I get the impression from a short dismissal like that that this script
>> is pretty hated :-(.
> I meant that it isn't valid currently; it was valid before the parallelisation
> patches. It would be nice if we could reconstruct the original order somehow.
> Without this patch the order is different every run though, and that makes
> comparing testresults unworkable.
>
>
Doesn't this patch make it always sort? And that should mean that -j1
will be the same as -JN again... ? it won't be the same order as
before the patches... but I doubt that is important... not that I'm
aware of anyway.
Andrew
Andrew
prev parent reply other threads:[~2014-10-02 19:05 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
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 [this message]
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=542DA1C3.7070607@redhat.com \
--to=amacleod@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rdsandiford@googlemail.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.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).