public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Joe Perches <joe@perches.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for MAINTAINERS: Add "B:" preferred bug reporting method (rev3)
Date: Wed, 27 Jan 2016 17:38:50 +0000	[thread overview]
Message-ID: <20160127173850.GA26687@strange.icx.intel.com> (raw)
In-Reply-To: <1453914984.10099.7.camel@perches.com>

On Wed, Jan 27, 2016 at 09:16:24AM -0800, Joe Perches wrote:
> On Wed, 2016-01-27 at 16:47 +0000, Patchwork wrote:
> > == Summary ==
> > 
> > Built on 5ae916607e3e12ba18c848dff42baaad5b118c4b drm-intel-nightly: 2016y-01m-27d-12h-48m-36s UTC integration manifest
> 
> I've no idea what this means.
> I'm not sure I care.
> Why send this to me?

We're experimenting with patchwork and trying to teach it about series
of patches and hooking automatic test systems to it. Unfortunately,
you've been the victim of a number of problems:

  - A mail of yours was parsed as a patch because it had a patch
    suggestion in it, which made that diff a candidate for automatic
    testing.
    http://lists.freedesktop.org/archives/intel-gfx/2016-January/085483.html

    I just fixed it manually, you shouldn't receive any more email. A
    better fix will land soon, your shouldn't have been a candidate for
    testing in the first place as we're supposed to only consider git
    send-email patches (an configuration option).

  - We still have a few flaky tests, so the test result was incoherent
    with just changing a text file

  - We may be to refine the system to not bother testing patches that
    don't touch code.

In case you are curious:

    http://patchwork.freedesktop.org/project/intel-gfx/series/
    http://patchwork.freedesktop.org/series/2539/

Sorry for the trouble,

-- 
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-27 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  9:10 [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Jani Nikula
2016-01-26 14:36 ` Joe Perches
2016-01-26 14:42 ` Joe Perches
2016-01-26 14:49   ` Richard Weinberger
2016-01-26 15:05     ` Jani Nikula
2016-01-26 14:55   ` Jani Nikula
2016-01-26 15:33   ` Dave Gordon
2016-01-26 20:14     ` Joe Perches
2016-01-27 16:47 ` ✗ Fi.CI.BAT: failure for MAINTAINERS: Add "B:" preferred bug reporting method (rev3) Patchwork
2016-01-27 17:16   ` Joe Perches
2016-01-27 17:38     ` Damien Lespiau [this message]
2016-01-27 17:03 ` ✓ Fi.CI.BAT: success " Patchwork
2016-01-28 14:06 ` Patchwork

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=20160127173850.GA26687@strange.icx.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joe@perches.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