All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables
Date: Wed, 16 Mar 2016 17:40:26 +0200	[thread overview]
Message-ID: <20160316154026.GO4329@intel.com> (raw)
In-Reply-To: <56E97D31.1010001@linux.intel.com>

On Wed, Mar 16, 2016 at 03:35:13PM +0000, Tvrtko Ursulin wrote:
> 
> On 16/03/16 15:01, Patchwork wrote:
> > == Series Details ==
> >
> > Series: series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables
> > URL   : https://patchwork.freedesktop.org/series/4508/
> > State : failure
> >
> > == Summary ==
> >
> > Series 4508v1 Series without cover letter
> > http://patchwork.freedesktop.org/api/1.0/series/4508/revisions/1/mbox/
> >
> > Test drv_module_reload_basic:
> >                  skip       -> PASS       (bdw-nuci7)
> > Test kms_flip:
> >          Subgroup basic-flip-vs-wf_vblank:
> >                  pass       -> FAIL       (ivb-t430s)
> 
> Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94294

I'd like people to add a bit more information to these analysis mails.
If there's just the bugzilla link I actually have to open it before
I can see what the problem was. Makes it harder to keep on top what
the most common BAT problems are.

> 
> >          Subgroup basic-plain-flip:
> >                  pass       -> DMESG-WARN (hsw-brixbox)
> 
> Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94349
> 
> > Test kms_frontbuffer_tracking:
> >          Subgroup basic:
> >                  dmesg-warn -> PASS       (hsw-brixbox)
> > Test kms_pipe_crc_basic:
> >          Subgroup nonblocking-crc-pipe-b-frame-sequence:
> >                  pass       -> DMESG-WARN (hsw-brixbox)
> 
> Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94384
> 
> >                  dmesg-warn -> PASS       (bdw-ultra)
> >          Subgroup read-crc-pipe-b:
> >                  dmesg-warn -> PASS       (hsw-gt2)
> >          Subgroup read-crc-pipe-b-frame-sequence:
> >                  dmesg-warn -> PASS       (hsw-brixbox)
> > Test pm_rpm:
> >          Subgroup basic-pci-d3-state:
> >                  fail       -> DMESG-FAIL (snb-x220t)
> 
> Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94349
> 
> >
> > bdw-nuci7        total:194  pass:182  dwarn:0   dfail:0   fail:0   skip:12
> > bdw-ultra        total:194  pass:173  dwarn:0   dfail:0   fail:0   skip:21
> > byt-nuc          total:194  pass:155  dwarn:4   dfail:0   fail:0   skip:35
> > hsw-brixbox      total:194  pass:170  dwarn:2   dfail:0   fail:0   skip:22
> > hsw-gt2          total:194  pass:177  dwarn:0   dfail:0   fail:0   skip:17
> > ivb-t430s        total:194  pass:168  dwarn:0   dfail:0   fail:1   skip:25
> > skl-i5k-2        total:194  pass:171  dwarn:0   dfail:0   fail:0   skip:23
> > skl-i7k-2        total:194  pass:171  dwarn:0   dfail:0   fail:0   skip:23
> > skl-nuci5        total:194  pass:183  dwarn:0   dfail:0   fail:0   skip:11
> > snb-x220t        total:194  pass:159  dwarn:1   dfail:1   fail:0   skip:33
> >
> > Results at /archive/results/CI_IGT_test/Patchwork_1616/
> >
> > a5c43f5d1b4968a370f54bdda5387ce213aca785 drm-intel-nightly: 2016y-03m-16d-14h-09m-03s UTC integration manifest
> > 12b10c002d2107d9c67685b4b94008145fe5e4e4 drm/i915: More renaming of rings to engines
> > 913a88b2b22fbc640542c5ce70128d6293063123 drm/i915: More intel_engine_cs renaming
> > 216f2de3f6d87d725cc437dc0b73f38bd4831c9e drm/i915: Rename intel_engine_cs struct members
> > 262439daabb6ce89701667f970b5179e5f487836 drm/i915: Rename intel_engine_cs function parameters
> > 4734cd9fd06a323fb7fd8468eaef529bb6dba052 drm/i915: Rename local struct intel_engine_cs variables
> 
> Series merged, thanks for the patch :) and review!
> 
> Regards,
> 
> Tvrtko
> 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-16 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 11:00 [PATCH 1/5] drm/i915: Rename local struct intel_engine_cs variables Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 2/5] drm/i915: Rename intel_engine_cs function parameters Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 3/5] drm/i915: Rename intel_engine_cs struct members Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 4/5] drm/i915: More intel_engine_cs renaming Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 5/5] drm/i915: More renaming of rings to engines Tvrtko Ursulin
2016-03-16 11:15   ` Chris Wilson
2016-03-16 15:01 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables Patchwork
2016-03-16 15:35   ` Tvrtko Ursulin
2016-03-16 15:40     ` Ville Syrjälä [this message]
2016-03-16 15:45       ` Tvrtko Ursulin
2016-03-16 15:56         ` Daniel Vetter
2016-03-16 16:40           ` Tvrtko Ursulin
2016-03-16 16:14         ` Ville Syrjälä

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=20160316154026.GO4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.