All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>
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: Wed, 29 Apr 2020 10:37:14 -0000	[thread overview]
Message-ID: <158815663424.6696.12195821963672181606@emeril.freedesktop.org> (raw)
In-Reply-To: <20200420130118.7a866fd5@canb.auug.org.au>

== Series Details ==

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

== Summary ==

CI Bug Log - changes from CI_DRM_8390 -> Patchwork_17505
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@i915_selftest@live@hangcheck:
    - fi-icl-y:           [PASS][1] -> [INCOMPLETE][2] ([i915#1580])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8390/fi-icl-y/igt@i915_selftest@live@hangcheck.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17505/fi-icl-y/igt@i915_selftest@live@hangcheck.html

  
  [i915#1580]: https://gitlab.freedesktop.org/drm/intel/issues/1580


Participating hosts (48 -> 42)
------------------------------

  Missing    (6): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7500u fi-ctg-p8600 fi-byt-clapper 


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

  * CI: CI-20190529 -> None
  * Linux: CI_DRM_8390 -> Patchwork_17505

  CI-20190529: 20190529
  CI_DRM_8390: 89473e10666c78c4df9e92c9caf03d7311c291cb @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5614: d095827add11d4e8158b87683971ee659749d9a4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_17505: 4cb00cc7b2f7e895d430b9bf376db1a803fddd6a @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

4cb00cc7b2f7 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_17505/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-04-29 10:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  3:01 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2020-04-20  3:01 ` [Intel-gfx] " Stephen Rothwell
2020-04-20  3:01 ` Stephen Rothwell
2020-04-28 22:33 ` Stephen Rothwell
2020-04-28 22:33   ` [Intel-gfx] " Stephen Rothwell
2020-04-28 22:33   ` Stephen Rothwell
2020-04-29  8:09   ` Bartlomiej Zolnierkiewicz
2020-04-29  8:09     ` [Intel-gfx] " Bartlomiej Zolnierkiewicz
2020-04-29  8:09     ` Bartlomiej Zolnierkiewicz
2020-04-29 10:50     ` Bartlomiej Zolnierkiewicz
2020-04-29 10:50       ` [Intel-gfx] " Bartlomiej Zolnierkiewicz
2020-04-29 10:50       ` Bartlomiej Zolnierkiewicz
2020-04-29 10:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-04-29 10:37 ` Patchwork [this message]
2020-04-29 12:56 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
  -- 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-11-02  1:43 Stephen Rothwell
2020-11-02  2:17 ` [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
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=158815663424.6696.12195821963672181606@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.