All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ltp: update to 20140828 release
Date: Fri, 31 Oct 2014 10:58:29 +0000	[thread overview]
Message-ID: <1414753109.7649.91.camel@ted> (raw)
In-Reply-To: <CAJTo0LY+r2qFgFmOmEXda1brymM8wpAfYFywsDAfWNtuedC+Ng@mail.gmail.com>

On Fri, 2014-10-31 at 09:44 +0000, Burton, Ross wrote:
> On 29 October 2014 08:38, Fathi Boudra <fathi.boudra@linaro.org>
> wrote:
>         bump SRCREV to 20140828 tag
>         drop automake-foreign patch - fixed upstream (commit 18594de
>         and edbae29)
>         update realtime tests fixes upstream status from submitted to
>         backported - merged upstream
>
> This doesn't build on the autobuilders, see for
> example https://autobuilder.yoctoproject.org/main/builders/minnow/builds/84/steps/BuildImages/logs/stdio
>
> There are hundreds of compiler warnings, and a missing header.

Now, since I've heard complaints that we don't merge patches quickly, I
want to highlight what this means.

We tried this patch, we found it had issues, therefore whenever we see
similar patches from similar authors, we now have a nagging doubt about
how much testing they've had. This means we when we aggregate those
patches there is more risk to the build, we need a clean build before we
merge patches so it can delay other people's patches. This is a bit of a
vicious circle and its why you see some of the behaviour we get
complaints about.

So I'd remind people that if they send things which don't work, it does
have an impact. There is also something you can do to influence this.

Cheers,

Richard




  reply	other threads:[~2014-10-31 10:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  8:38 [PATCH] ltp: update to 20140828 release Fathi Boudra
2014-10-31  9:44 ` Burton, Ross
2014-10-31 10:58   ` Richard Purdie [this message]
2014-10-31 12:46     ` Fathi Boudra
2014-10-31 20:09       ` Burton, Ross
2014-11-04 15:10         ` Fathi Boudra
2014-11-04 15:54           ` Richard Purdie
2014-11-05 10:20             ` Fathi Boudra
2014-11-05 10:33               ` Burton, Ross

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=1414753109.7649.91.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.