From: Richard Guenther <richard.guenther@gmail.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, janisjo@codesourcery.com
Subject: Re: RFC: Improving support for known testsuite failures
Date: Thu, 08 Sep 2011 12:30:00 -0000 [thread overview]
Message-ID: <CAFiYyc0O8ovrkpX+3OrrW8ZDn28qcSY0ZRKaifpjesZ-NaXPKg@mail.gmail.com> (raw)
In-Reply-To: <CAD_=9DTTB3FqMS-UULZrYHCe4Ar8-ANTmRaGo+FUfC5s4enBeA@mail.gmail.com>
On Thu, Sep 8, 2011 at 2:26 PM, Diego Novillo <dnovillo@google.com> wrote:
> On Thu, Sep 8, 2011 at 08:20, Richard Guenther
> <richard.guenther@gmail.com> wrote:
>
>> Cache the comparison result? If you specify a (minimum) revision
>> required for testing just test against a cached revision that fulfils
>> the requirement. Something I never implemented for ours.
>
> Nope. Build must be functionally independent from other state. If
> the manifest of known failures lives together with the source code,
> that's acceptable. Depending on previous builds is not.
It _does_ live with the source code. Think of implicitly "checking in" the
build result with the tested revision. That's not different from your idea
of checking in some sort of whitelist of fails.
> This also
> helps individual developers doing builds and packagers doing spins off
> of the main source branches.
A svn revision is unique. Or do you mean in other _repositories_?
Then the repository:revision combination is unique. You don't
test whole source tarballs, do you?
Richard.
>
> Diego.
>
next prev parent reply other threads:[~2011-09-08 12:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 15:28 Diego Novillo
2011-09-07 18:43 ` Andreas Jaeger
2011-09-07 19:57 ` Joseph S. Myers
2011-09-08 8:31 ` Richard Guenther
2011-09-08 11:05 ` Diego Novillo
2011-09-08 11:16 ` Richard Guenther
2011-09-08 11:34 ` Diego Novillo
2011-09-08 11:49 ` Richard Guenther
2011-09-08 12:14 ` Diego Novillo
2011-09-08 12:20 ` Richard Guenther
2011-09-08 12:26 ` Diego Novillo
2011-09-08 12:30 ` Richard Guenther [this message]
2011-09-08 12:33 ` Diego Novillo
2011-09-08 13:24 ` Richard Earnshaw
2011-09-08 13:55 ` Diego Novillo
2011-09-08 14:03 ` Richard Earnshaw
2011-09-08 16:41 ` Joseph S. Myers
2011-09-23 0:07 ` Hans-Peter Nilsson
2011-09-23 13:11 ` Diego Novillo
2011-09-08 16:39 ` Joseph S. Myers
2011-09-08 22:27 ` Michael Hope
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=CAFiYyc0O8ovrkpX+3OrrW8ZDn28qcSY0ZRKaifpjesZ-NaXPKg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=janisjo@codesourcery.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).