All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for linux-next: build failure after merge of the drm-misc tree
Date: Mon, 02 Nov 2020 02:17:02 -0000	[thread overview]
Message-ID: <160428342261.26395.1001876088500336515@emeril.freedesktop.org> (raw)
In-Reply-To: <20201102124327.2f82b2a7@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 4706 bytes --]

== Series Details ==

Series: linux-next: build failure after merge of the drm-misc tree
URL   : https://patchwork.freedesktop.org/series/83323/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9238 -> Patchwork_18823
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/index.html

New tests
---------

  New tests have been introduced between CI_DRM_9238 and Patchwork_18823:

### New CI tests (1) ###

  * boot:
    - Statuses : 38 pass(s)
    - Exec time: [0.0] s

  

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

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

### IGT changes ###

#### Issues hit ####

  * igt@core_hotunplug@unbind-rebind:
    - fi-blb-e6850:       [PASS][1] -> [INCOMPLETE][2] ([i915#2540])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-blb-e6850/igt@core_hotunplug@unbind-rebind.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-blb-e6850/igt@core_hotunplug@unbind-rebind.html

  * igt@i915_pm_rpm@basic-pci-d3-state:
    - fi-bsw-kefka:       [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html

  * igt@kms_chamelium@dp-crc-fast:
    - fi-icl-u2:          [PASS][5] -> [FAIL][6] ([i915#1161] / [i915#262])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-icl-u2/igt@kms_chamelium@dp-crc-fast.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-icl-u2/igt@kms_chamelium@dp-crc-fast.html

  
#### Possible fixes ####

  * igt@i915_module_load@reload:
    - fi-byt-j1900:       [DMESG-WARN][7] ([i915#1982]) -> [PASS][8] +1 similar issue
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-byt-j1900/igt@i915_module_load@reload.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-byt-j1900/igt@i915_module_load@reload.html

  * igt@i915_pm_rpm@basic-pci-d3-state:
    - fi-bsw-n3050:       [DMESG-WARN][9] ([i915#1982]) -> [PASS][10]
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-bsw-n3050/igt@i915_pm_rpm@basic-pci-d3-state.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-bsw-n3050/igt@i915_pm_rpm@basic-pci-d3-state.html

  * igt@i915_pm_rpm@module-reload:
    - fi-skl-lmem:        [DMESG-WARN][11] -> [PASS][12]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html

  * igt@kms_chamelium@dp-crc-fast:
    - fi-cml-u2:          [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html

  * igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
    - fi-icl-u2:          [DMESG-WARN][15] ([i915#1982]) -> [PASS][16] +2 similar issues
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9238/fi-icl-u2/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/fi-icl-u2/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html

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

  [i915#1161]: https://gitlab.freedesktop.org/drm/intel/issues/1161
  [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
  [i915#2540]: https://gitlab.freedesktop.org/drm/intel/issues/2540
  [i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262


Participating hosts (42 -> 38)
------------------------------

  Missing    (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u 


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

  * Linux: CI_DRM_9238 -> Patchwork_18823

  CI-20190529: 20190529
  CI_DRM_9238: acdb28c0a634b8dcf8c6946de851a25d1c532b10 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5830: 12d370cb57e0cfcb781c87ad9e15e68b17a1f41f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_18823: 667a901ef4195e9b22d86f496a7217535bd827c0 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

667a901ef419 linux-next: build failure after merge of the drm-misc tree

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18823/index.html

[-- Attachment #1.2: Type: text/html, Size: 5815 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  parent reply	other threads:[~2020-11-02  2:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  1:43 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2020-11-02  1:43 ` [Intel-gfx] " Stephen Rothwell
2020-11-02  1:43 ` Stephen Rothwell
2020-11-02  1:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-11-02  2:17 ` Patchwork [this message]
2020-11-02  3:52 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-11-02  9:28 ` Daniel Vetter
2020-11-02  9:28   ` [Intel-gfx] " Daniel Vetter
2020-11-02  9:28   ` Daniel Vetter
2020-11-02 10:23   ` Michael S. Tsirkin
2020-11-02 10:23     ` [Intel-gfx] " Michael S. Tsirkin
2020-11-02 10:23     ` Michael S. Tsirkin
2020-11-02 10:28     ` Daniel Vetter
2020-11-02 10:28       ` [Intel-gfx] " Daniel Vetter
2020-11-02 10:28       ` Daniel Vetter
2020-11-02 10:27   ` Christoph Hellwig
2020-11-02 10:27     ` [Intel-gfx] " Christoph Hellwig
2020-11-02 11:05     ` Michael S. Tsirkin
2020-11-02 11:05       ` [Intel-gfx] " Michael S. Tsirkin
2020-11-02 11:05       ` Michael S. Tsirkin
2020-11-02 10:19 ` Michael S. Tsirkin
2020-11-02 10:19   ` [Intel-gfx] " Michael S. Tsirkin
2020-11-02 10:19   ` Michael S. Tsirkin
2020-11-11  6:10   ` Stephen Rothwell
2020-11-11  6:10     ` [Intel-gfx] " Stephen Rothwell
2020-11-11  6:10     ` Stephen Rothwell
2020-11-11 12:48     ` Michael S. Tsirkin
2020-11-11 12:48       ` [Intel-gfx] " Michael S. Tsirkin
2020-11-11 12:48       ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2022-11-10  0:10 Stephen Rothwell
2022-11-10 21:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-04-06  0:50 Stephen Rothwell
2022-04-06  3:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-15  9:26 Stephen Rothwell
2021-10-15 12:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-17  0:59 Stephen Rothwell
2020-06-17  2:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-04-20  3:01 Stephen Rothwell
2020-04-29 10:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-16  1:23 Stephen Rothwell
2019-12-16  2:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " 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=160428342261.26395.1001876088500336515@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sfr@canb.auug.org.au \
    /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.