All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe id following atomic guidelines (rev3)
Date: Thu, 29 Nov 2018 13:23:35 -0800	[thread overview]
Message-ID: <20181129212335.GM8630@intel.com> (raw)
In-Reply-To: <fa27c7c13a88c6c27b36905d5b75ab8c9b4239bc.camel@intel.com>

On Thu, Nov 29, 2018 at 08:26:31PM +0000, Souza, Jose wrote:
> On Thu, 2018-11-29 at 06:33 +0000, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: drm/i915/psr: Get pipe id following atomic guidelines (rev3)
> > URL   : https://patchwork.freedesktop.org/series/53132/
> > State : failure
> > 
> > == Summary ==
> > 
> > CI Bug Log - changes from CI_DRM_5220 -> Patchwork_10945
> > ====================================================
> > 
> > Summary
> > -------
> > 
> >   **FAILURE**
> > 
> >   Serious unknown changes coming with Patchwork_10945 absolutely need
> > to be
> >   verified manually.
> >   
> >   If you think the reported changes have nothing to do with the
> > changes
> >   introduced in Patchwork_10945, please notify your bug team to allow
> > them
> >   to document this new failure mode, which will reduce false
> > positives in CI.
> > 
> >   External URL: 
> > https://patchwork.freedesktop.org/api/1.0/series/53132/revisions/3/mbox/
> > 
> > Possible new issues
> > -------------------
> > 
> >   Here are the unknown changes that may have been introduced in
> > Patchwork_10945:
> > 
> > ### IGT changes ###
> > 
> > #### Possible regressions ####
> > 
> >   * igt@gem_close_race@basic-threads:
> >     - fi-bsw-kefka:       PASS -> INCOMPLETE
> 
> Unrelated to the patch and looks like the machine died as no other test
> ran.

I agree...
so, I'm ignoring this message:
"THIS SERIES REVISION IS A RERUN. Please don't overuse the "test again" button."

and just hit "test again"

> 
> > 
> >   
> > Known issues
> > ------------
> > 
> >   Here are the changes found in Patchwork_10945 that come from known
> > issues:
> > 
> > ### IGT changes ###
> > 
> > #### Issues hit ####
> > 
> >   * igt@kms_frontbuffer_tracking@basic:
> >     - fi-hsw-peppy:       PASS -> DMESG-WARN [fdo#102614]
> > 
> >   
> > #### Possible fixes ####
> > 
> >   * igt@kms_frontbuffer_tracking@basic:
> >     - fi-byt-clapper:     FAIL [fdo#103167] -> PASS
> > 
> >   * igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence:
> >     - fi-byt-clapper:     FAIL [fdo#103191] / [fdo#107362] -> PASS
> > 
> >   
> >   [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
> >   [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
> >   [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
> >   [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
> > 
> > 
> > Participating hosts (49 -> 44)
> > ------------------------------
> > 
> >   Additional (1): fi-byt-j1900 
> >   Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-
> > squawks fi-bsw-cyan fi-ctg-p8600 
> > 
> > 
> > Build changes
> > -------------
> > 
> >     * Linux: CI_DRM_5220 -> Patchwork_10945
> > 
> >   CI_DRM_5220: b3a448de6828d0bd0397318d15ec143a3dfb553a @
> > git://anongit.freedesktop.org/gfx-ci/linux
> >   IGT_4735: b05c028ccdb6ac8e8d8499a041bb14dfe358ee26 @
> > git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> >   Patchwork_10945: 6f9263b860081021f1915f2a547d3cf9b3e0bcd7 @
> > git://anongit.freedesktop.org/gfx-ci/linux
> > 
> > 
> > == Linux commits ==
> > 
> > 6f9263b86008 drm/i915/psr: Get pipe id following atomic guidelines
> > 
> > == Logs ==
> > 
> > For more details see: 
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10945/



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

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

  reply	other threads:[~2018-11-29 21:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28  7:28 [PATCH] drm/i915/psr: Get pipe id following atomic guidelines José Roberto de Souza
2018-11-28  7:55 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-11-28  8:23 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-28 15:14 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-11-28 16:55 ` [PATCH] " Rodrigo Vivi
2018-11-28 18:21   ` Souza, Jose
2018-11-28 18:44     ` Rodrigo Vivi
2018-11-28 20:47 ` ✗ Fi.CI.SPARSE: warning for drm/i915/psr: Get pipe id following atomic guidelines (rev2) Patchwork
2018-11-28 21:02 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-28 22:13   ` Souza, Jose
2018-11-29  6:18     ` Rodrigo Vivi
2018-11-29  7:52       ` Saarinen, Jani
2018-11-29 17:36         ` Rodrigo Vivi
2018-11-30 13:04           ` Martin Peres
2018-11-30 17:26             ` Rodrigo Vivi
2018-12-03 12:29               ` Peres, Martin
2018-12-03 20:55                 ` Rodrigo Vivi
2018-12-04 11:25                   ` Peres, Martin
2018-11-28 21:25 ` [PATCH] drm/i915/psr: Get pipe id following atomic guidelines Ville Syrjälä
2018-11-29  6:17 ` ✗ Fi.CI.SPARSE: warning for drm/i915/psr: Get pipe id following atomic guidelines (rev3) Patchwork
2018-11-29  6:33 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-29 20:26   ` Souza, Jose
2018-11-29 21:23     ` Rodrigo Vivi [this message]
2018-11-29 22:05 ` ✗ Fi.CI.SPARSE: warning for drm/i915/psr: Get pipe id following atomic guidelines (rev4) Patchwork
2018-11-29 22:26 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-29 23:39   ` Rodrigo Vivi
2018-11-29 23:37 ` ✗ Fi.CI.SPARSE: warning for drm/i915/psr: Get pipe id following atomic guidelines (rev5) Patchwork
2018-11-29 23:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-30 18:05   ` Souza, Jose
2018-11-30 19:02 ` ✓ Fi.CI.IGT: " 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=20181129212335.GM8630@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@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.