All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,1/4] package/spice: disable tests
Date: Tue, 19 Nov 2019 09:15:27 +0100	[thread overview]
Message-ID: <20191119091527.5e9c6806@windsurf.home> (raw)
In-Reply-To: <CAPi7W82J2ehtREVFUkdMcn9rwy2pvBEmAhDzmCcCkbD3=vWGGQ@mail.gmail.com>

On Tue, 19 Nov 2019 08:47:52 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> > I've applied to next. However, your patch to upstream is not really
> > complete, or at least an additional patch is needed: when tests are
> > enabled, their configure.ac script should check if gdk-pixbuf is
> > available. And if it's not available, it should bail out, or disable
> > tests, but not allow the configure process to complete, and then have a
> > build failure when compiling.  
> You applied only the first patch of the serie

Yes, I didn't get around to applying the rest of the series.

> and you applied it on next even if it fixes a build failure on master. Was it intentional?

I was not sure if it was a build failure on master, and the autobuilder
failure linked in the commit log
(http://autobuild.buildroot.org/results/96c786f85d35f33508e9c71778043d16b87f72cd)
happened on the next branch. I'll cherry-pick on master.

In such cases (i.e autobuilder failures happening on next, but issue
also present in master), it's always good to be explicit in the patch,
by adding a small note like this:

"""
balblabla

Signed-off-by: John Doe <john.doe@foobar.org>
---
The autobuilder failure linked in the commit log was for next, but the
problem also exists on master.
"""

This would really help.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-19  8:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 16:44 [Buildroot] [PATCH v2,1/4] package/spice: disable tests Fabrice Fontaine
2019-11-17 16:44 ` [Buildroot] [PATCH v2,2/4] package/celt051: needs dynamic library Fabrice Fontaine
2019-11-23 13:38   ` [Buildroot] [PATCH v2, 2/4] " Peter Korsgaard
2019-11-23 16:05     ` Fabrice Fontaine
2020-01-23 22:23       ` Arnout Vandecappelle
2020-01-24 18:14         ` Yann E. MORIN
2020-01-27 16:22           ` Arnout Vandecappelle
2020-01-27 16:25             ` Fabrice Fontaine
2019-11-17 16:44 ` [Buildroot] [PATCH v2, 3/4] package/spice-protocol: bump to version 0.14.0 Fabrice Fontaine
2019-11-23 13:33   ` Peter Korsgaard
2019-12-03  9:49   ` Peter Korsgaard
2019-12-03 10:08     ` Baruch Siach
2019-12-03 12:15       ` Peter Korsgaard
2019-11-17 16:44 ` [Buildroot] [PATCH v2, 4/4] package/spice: security bump to version 0.14.2 Fabrice Fontaine
2019-11-23 13:33   ` Peter Korsgaard
2019-12-03  9:49   ` Peter Korsgaard
2019-11-18 21:47 ` [Buildroot] [PATCH v2,1/4] package/spice: disable tests Thomas Petazzoni
2019-11-19  7:47   ` Fabrice Fontaine
2019-11-19  8:15     ` Thomas Petazzoni [this message]
2019-11-22 22:14 ` Peter Korsgaard

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=20191119091527.5e9c6806@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.