public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Petr Mladek <pmladek@suse.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for RFC: console: hack up console_lock more v3 (rev4)
Date: Fri, 10 May 2019 11:44:43 -0000	[thread overview]
Message-ID: <20190510114443.17664.8443@emeril.freedesktop.org> (raw)
In-Reply-To: <20190509120903.28939-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: RFC: console: hack up console_lock more v3 (rev4)
URL   : https://patchwork.freedesktop.org/series/60467/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_6073 -> Patchwork_13001
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with Patchwork_13001 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_13001, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13001/

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in Patchwork_13001:

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_sanitycheck:
    - fi-skl-lmem:        [PASS][1] -> [INCOMPLETE][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6073/fi-skl-lmem/igt@i915_selftest@live_sanitycheck.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13001/fi-skl-lmem/igt@i915_selftest@live_sanitycheck.html

  
Known issues
------------

  Here are the changes found in Patchwork_13001 that come from known issues:

### IGT changes ###

#### Possible fixes ####

  * igt@i915_selftest@live_contexts:
    - fi-bdw-gvtdvm:      [DMESG-FAIL][3] ([fdo#110235]) -> [PASS][4]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6073/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13001/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html

  * igt@i915_selftest@live_hangcheck:
    - {fi-icl-u2}:        [INCOMPLETE][5] ([fdo#107713] / [fdo#108569]) -> [PASS][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6073/fi-icl-u2/igt@i915_selftest@live_hangcheck.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13001/fi-icl-u2/igt@i915_selftest@live_hangcheck.html

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
  [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
  [fdo#110235]: https://bugs.freedesktop.org/show_bug.cgi?id=110235


Participating hosts (47 -> 43)
------------------------------

  Additional (3): fi-icl-y fi-blb-e6850 fi-apl-guc 
  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7500u fi-pnv-d510 fi-byt-clapper 


Build changes
-------------

  * Linux: CI_DRM_6073 -> Patchwork_13001

  CI_DRM_6073: c059ddabfe60a5072ace44a34a9de9b4202df6ec @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4978: b9b3646d4f04dd0204ead2a1a10f9e1806a0b622 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_13001: 7e7042b1b9a60db79de8464000c3bfe5016e054f @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

7e7042b1b9a6 RFC: console: hack up console_lock more v3

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13001/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2019-05-10 11:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 12:09 [PATCH] RFC: console: hack up console_lock more v3 Daniel Vetter
2019-05-09 12:21 ` Chris Wilson
2019-05-09 12:31 ` Peter Zijlstra
2019-05-09 13:06   ` Daniel Vetter
2019-05-09 13:36     ` Peter Zijlstra
2019-05-09 14:56 ` Petr Mladek
2019-05-09 16:43   ` Daniel Vetter
2019-05-10  9:15     ` Petr Mladek
2019-05-10  9:51       ` Sergey Senozhatsky
2019-05-10 15:05       ` Daniel Vetter
2019-05-09 15:14 ` ✗ Fi.CI.BAT: failure for RFC: console: hack up console_lock more v3 (rev2) Patchwork
2019-05-09 20:06 ` [PATCH] kernel/locking/semaphore: use wake_q in up() Daniel Vetter
2019-05-10  5:50   ` Sergey Senozhatsky
2019-05-10  7:51     ` Daniel Vetter
2019-05-10  9:28   ` Petr Mladek
2019-05-10 15:20     ` Daniel Vetter
2019-05-15 11:53       ` Petr Mladek
2019-05-09 20:41 ` ✓ Fi.CI.BAT: success for RFC: console: hack up console_lock more v3 (rev3) Patchwork
2019-05-10  6:33 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-10 11:23 ` ✗ Fi.CI.CHECKPATCH: warning for RFC: console: hack up console_lock more v3 (rev4) Patchwork
2019-05-10 11:44 ` Patchwork [this message]

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=20190510114443.17664.8443@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pmladek@suse.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