From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for RFC: console: hack up console_trylock more (rev2)
Date: Mon, 06 May 2019 08:30:29 -0000 [thread overview]
Message-ID: <20190506083029.16844.35552@emeril.freedesktop.org> (raw)
In-Reply-To: <20190502141643.21080-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: RFC: console: hack up console_trylock more (rev2)
URL : https://patchwork.freedesktop.org/series/60212/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6048 -> Patchwork_12968
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_12968 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_12968, 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_12968/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12968:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live_hangcheck:
- fi-apl-guc: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6048/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
#### Warnings ####
* igt@runner@aborted:
- fi-apl-guc: [FAIL][3] ([fdo#108622] / [fdo#109720]) -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6048/fi-apl-guc/igt@runner@aborted.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/fi-apl-guc/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_12968 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_workarounds:
- fi-icl-y: [PASS][5] -> [INCOMPLETE][6] ([fdo#107713] / [fdo#110581])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6048/fi-icl-y/igt@i915_selftest@live_workarounds.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/fi-icl-y/igt@i915_selftest@live_workarounds.html
#### Possible fixes ####
* igt@i915_selftest@live_execlists:
- fi-apl-guc: [INCOMPLETE][7] ([fdo#103927] / [fdo#109720] / [fdo#110581]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6048/fi-apl-guc/igt@i915_selftest@live_execlists.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/fi-apl-guc/igt@i915_selftest@live_execlists.html
* igt@kms_flip@basic-flip-vs-wf_vblank:
- fi-bwr-2160: [FAIL][9] ([fdo#100368]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6048/fi-bwr-2160/igt@kms_flip@basic-flip-vs-wf_vblank.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/fi-bwr-2160/igt@kms_flip@basic-flip-vs-wf_vblank.html
[fdo#100368]: https://bugs.freedesktop.org/show_bug.cgi?id=100368
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108622]: https://bugs.freedesktop.org/show_bug.cgi?id=108622
[fdo#109720]: https://bugs.freedesktop.org/show_bug.cgi?id=109720
[fdo#110581]: https://bugs.freedesktop.org/show_bug.cgi?id=110581
Participating hosts (52 -> 45)
------------------------------
Additional (1): fi-bsw-n3050
Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_6048 -> Patchwork_12968
CI_DRM_6048: 896b156d0aa15d20a798e528ff7e5d529fbf26ae @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4972: f052e49a43cc9704ea5f240df15dd9d3dfed68ab @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12968: 679d117ff9c33340493d143534e192ce490943dc @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
679d117ff9c3 RFC: console: hack up console_lock more v2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12968/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-05-06 8:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 14:16 [PATCH] RFC: console: hack up console_trylock more Daniel Vetter
2019-05-02 15:15 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-05-02 15:50 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-02 20:16 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-03 15:14 ` [PATCH] " Petr Mladek
2019-05-06 7:11 ` Daniel Vetter
2019-05-06 7:48 ` Petr Mladek
2019-05-06 8:40 ` Daniel Vetter
2019-05-06 7:45 ` [PATCH] RFC: console: hack up console_lock more v2 Daniel Vetter
2019-05-06 8:16 ` Petr Mladek
2019-05-06 8:26 ` Petr Mladek
2019-05-06 9:38 ` Daniel Vetter
2019-05-06 11:24 ` Petr Mladek
2019-05-08 8:17 ` [Intel-gfx] " Daniel Vetter
2019-05-09 15:08 ` Petr Mladek
2019-05-06 8:20 ` Petr Mladek
2019-05-09 10:32 ` [Intel-gfx] " Chris Wilson
2019-05-09 13:05 ` Peter Zijlstra
2019-05-06 8:08 ` ✗ Fi.CI.CHECKPATCH: warning for RFC: console: hack up console_trylock more (rev2) Patchwork
2019-05-06 8:30 ` 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=20190506083029.16844.35552@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox