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 (rev2)
Date: Wed, 28 Nov 2018 22:18:04 -0800 [thread overview]
Message-ID: <20181129061804.GD2024@intel.com> (raw)
In-Reply-To: <d57b11c5d515f6b54a0492cb20c514c2f0ced8d0.camel@intel.com>
On Wed, Nov 28, 2018 at 02:13:12PM -0800, Souza, Jose wrote:
> On Wed, 2018-11-28 at 21:02 +0000, Patchwork wrote:
> > == Series Details ==
> >
> > Series: drm/i915/psr: Get pipe id following atomic guidelines (rev2)
> > URL : https://patchwork.freedesktop.org/series/53132/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from CI_DRM_5216 -> Patchwork_10934
> > ====================================================
> >
> > Summary
> > -------
> >
> > **FAILURE**
> >
> > Serious unknown changes coming with Patchwork_10934 absolutely need
> > to be
> > verified manually.
> >
> > If you think the reported changes have nothing to do with the
> > changes
> > introduced in Patchwork_10934, 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/2/mbox/
> >
> > Possible new issues
> > -------------------
> >
> > Here are the unknown changes that may have been introduced in
> > Patchwork_10934:
> >
> > ### IGT changes ###
> >
> > #### Possible regressions ####
> >
> > * igt@i915_selftest@live_sanitycheck:
> > - fi-apl-guc: PASS -> DMESG-WARN
> >
> > * {igt@runner@aborted}:
> > - fi-apl-guc: NOTRUN -> FAIL
>
> Both are pretty much non related with display, what do you think
> Rodrigo? It is a merge blocker?
I got addicted to see all green on CI. So I always prefer to
trigger a retest. So anyone following the link that is merged with
the patch doens't have to understand and analyze why it was merged
with BAT failure.
I just triggered the re-test for this patch.
Thanks,
Rodrigo.
>
> >
> >
> > Known issues
> > ------------
> >
> > Here are the changes found in Patchwork_10934 that come from known
> > issues:
> >
> > ### IGT changes ###
> >
> > #### Issues hit ####
> >
> > * igt@i915_selftest@live_hangcheck:
> > - fi-kbl-7560u: PASS -> INCOMPLETE [fdo#108044]
> >
> > * igt@kms_pipe_crc_basic@read-crc-pipe-a:
> > - fi-byt-clapper: PASS -> FAIL [fdo#107362]
> >
> >
> > {name}: This element is suppressed. This means it is ignored when
> > computing
> > the status of the difference (SUCCESS, WARNING, or
> > FAILURE).
> >
> > [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
> > [fdo#108044]: https://bugs.freedesktop.org/show_bug.cgi?id=108044
> >
> >
> > Participating hosts (50 -> 44)
> > ------------------------------
> >
> > 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_5216 -> Patchwork_10934
> >
> > CI_DRM_5216: 2236cef56d19627516af1f1b19b155d65fbc9834 @
> > git://anongit.freedesktop.org/gfx-ci/linux
> > IGT_4735: b05c028ccdb6ac8e8d8499a041bb14dfe358ee26 @
> > git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> > Patchwork_10934: 2ebde49b2d0906d8106b020a2b0480bc5f552a01 @
> > git://anongit.freedesktop.org/gfx-ci/linux
> >
> >
> > == Linux commits ==
> >
> > 2ebde49b2d09 drm/i915/psr: Get pipe id following atomic guidelines
> >
> > == Logs ==
> >
> > For more details see:
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10934/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-29 6:18 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 [this message]
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
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=20181129061804.GD2024@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).