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, 16 Dec 2019 02:02:54 -0000 [thread overview]
Message-ID: <157646177449.5612.5279089004874257160@emeril.freedesktop.org> (raw)
In-Reply-To: <20191216122331.43c766f1@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/70958/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7569 -> Patchwork_15782
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/index.html
Known issues
------------
Here are the changes found in Patchwork_15782 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_blt:
- fi-hsw-4770r: [PASS][1] -> [DMESG-FAIL][2] ([i915#553] / [i915#725])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7569/fi-hsw-4770r/igt@i915_selftest@live_blt.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/fi-hsw-4770r/igt@i915_selftest@live_blt.html
#### Possible fixes ####
* igt@gem_close_race@basic-threads:
- fi-byt-j1900: [TIMEOUT][3] ([i915#816]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7569/fi-byt-j1900/igt@gem_close_race@basic-threads.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/fi-byt-j1900/igt@gem_close_race@basic-threads.html
* igt@i915_selftest@live_gem_contexts:
- fi-hsw-peppy: [DMESG-FAIL][5] ([i915#722]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7569/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
- fi-byt-n2820: [INCOMPLETE][7] ([i915#45]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7569/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
* igt@kms_flip@basic-flip-vs-dpms:
- fi-apl-guc: [DMESG-WARN][9] ([i915#180]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7569/fi-apl-guc/igt@kms_flip@basic-flip-vs-dpms.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15782/fi-apl-guc/igt@kms_flip@basic-flip-vs-dpms.html
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
[i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
[i915#722]: https://gitlab.freedesktop.org/drm/intel/issues/722
[i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
[i915#816]: https://gitlab.freedesktop.org/drm/intel/issues/816
Participating hosts (34 -> 24)
------------------------------
Missing (10): fi-icl-1065g7 fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-bwr-2160 fi-ctg-p8600 fi-byt-clapper fi-bdw-samus fi-snb-2600
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7569 -> Patchwork_15782
CI-20190529: 20190529
CI_DRM_7569: 62c2abc0df8983aba79ba093413683c44e9c4748 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5349: 048f58513d8b8ec6bb307a939f0ac959bc0f0e10 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15782: ccba0d4a341ccc5d1f1cc335d50723e251e787e1 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
ccba0d4a341c 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_15782/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-16 2:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 1:23 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2019-12-16 1:23 ` [Intel-gfx] " Stephen Rothwell
2019-12-16 1:23 ` Stephen Rothwell
2019-12-16 1:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-12-16 2:02 ` Patchwork [this message]
2019-12-16 3:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2019-12-17 13:19 ` Daniel Vetter
2019-12-17 13:19 ` [Intel-gfx] " Daniel Vetter
2019-12-17 13:19 ` Daniel Vetter
2019-12-17 20:22 ` Stephen Rothwell
2019-12-17 20:22 ` [Intel-gfx] " Stephen Rothwell
2019-12-17 20:22 ` Stephen Rothwell
2019-12-18 11:53 ` Daniel Vetter
2019-12-18 11:53 ` [Intel-gfx] " Daniel Vetter
2019-12-18 11:53 ` Daniel Vetter
2020-04-20 3:01 Stephen Rothwell
2020-04-29 10:37 ` [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-11-02 1:43 Stephen Rothwell
2020-11-02 2:17 ` [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
2022-04-06 0:50 Stephen Rothwell
2022-04-06 3:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-11-10 0:10 Stephen Rothwell
2022-11-10 21:13 ` [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=157646177449.5612.5279089004874257160@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.