From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org,
Martin Peres <martin.peres@linux.intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe id following atomic guidelines (rev4)
Date: Thu, 29 Nov 2018 15:39:51 -0800 [thread overview]
Message-ID: <20181129233951.GX8630@intel.com> (raw)
In-Reply-To: <20181129222604.5828.26268@emeril.freedesktop.org>
On Thu, Nov 29, 2018 at 10:26:04PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/psr: Get pipe id following atomic guidelines (rev4)
> URL : https://patchwork.freedesktop.org/series/53132/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5226 -> Patchwork_10966
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_10966 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_10966, 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/4/mbox/
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_10966:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live_guc:
> - fi-gdg-551: PASS -> INCOMPLETE
Martin, any recommendation here?
4th non-related failure in a row...
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_10966 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_exec_suspend@basic-s4-devices:
> - fi-ivb-3520m: PASS -> FAIL [fdo#108880]
>
> * igt@i915_selftest@live_coherency:
> - fi-gdg-551: PASS -> DMESG-FAIL [fdo#107164]
>
> * igt@i915_selftest@live_execlists:
> - fi-apl-guc: PASS -> INCOMPLETE [fdo#103927]
>
>
> #### Possible fixes ####
>
> * igt@gem_ctx_create@basic-files:
> - fi-bsw-n3050: FAIL [fdo#108656] -> PASS
>
> * igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence:
> - fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
>
>
> [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
> [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
> [fdo#107164]: https://bugs.freedesktop.org/show_bug.cgi?id=107164
> [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
> [fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
> [fdo#108880]: https://bugs.freedesktop.org/show_bug.cgi?id=108880
>
>
> Participating hosts (49 -> 42)
> ------------------------------
>
> Missing (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_5226 -> Patchwork_10966
>
> CI_DRM_5226: 70ad55640e884b31fb19a0e73fa68cb9c99a69f0 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_10966: 8471677d0c78ba54d7902c5959f5ca224ab59aba @ git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Linux commits ==
>
> 8471677d0c78 drm/i915/psr: Get pipe id following atomic guidelines
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10966/
> _______________________________________________
> 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
next prev parent reply other threads:[~2018-11-29 23:39 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
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 [this message]
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=20181129233951.GX8630@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=martin.peres@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.