From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.IGT: failure for lib/ioctl_wrappers: Remove static variables for getting params
Date: Wed, 04 Dec 2019 15:03:02 -0000 [thread overview]
Message-ID: <157547178237.12194.2569602359543035344@emeril.freedesktop.org> (raw)
In-Reply-To: <20191204080649.27688-1-zbigniew.kempczynski@intel.com>
== Series Details ==
Series: lib/ioctl_wrappers: Remove static variables for getting params
URL : https://patchwork.freedesktop.org/series/70416/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7480_full -> IGTPW_3803_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_3803_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_3803_full, 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/IGTPW_3803/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3803_full:
### IGT changes ###
#### Possible regressions ####
* igt@runner@aborted:
- shard-apl: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-apl8/igt@runner@aborted.html
Known issues
------------
Here are the changes found in IGTPW_3803_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-snb: [PASS][2] -> [DMESG-WARN][3] ([fdo#111870])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][4] -> [INCOMPLETE][5] ([i915#58] / [k.org#198133])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-glk6/igt@kms_big_fb@linear-64bpp-rotate-180.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-glk2/igt@kms_big_fb@linear-64bpp-rotate-180.html
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-apl: [PASS][6] -> [DMESG-WARN][7] ([i915#180]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-apl1/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-apl1/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
* igt@perf@disabled-read-error:
- shard-hsw: [PASS][8] -> [INCOMPLETE][9] ([i915#61])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-hsw5/igt@perf@disabled-read-error.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-hsw6/igt@perf@disabled-read-error.html
#### Possible fixes ####
* igt@gem_exec_parallel@vcs0-contexts:
- shard-hsw: [FAIL][10] ([i915#676]) -> [PASS][11] +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-hsw5/igt@gem_exec_parallel@vcs0-contexts.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-hsw5/igt@gem_exec_parallel@vcs0-contexts.html
* {igt@gem_exec_parse_blt@bb-start-cmd}:
- shard-glk: [TIMEOUT][12] ([fdo#112271]) -> [PASS][13] +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-glk6/igt@gem_exec_parse_blt@bb-start-cmd.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-glk7/igt@gem_exec_parse_blt@bb-start-cmd.html
* igt@gem_persistent_relocs@forked-thrash-inactive:
- shard-snb: [TIMEOUT][14] ([i915#530]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-snb4/igt@gem_persistent_relocs@forked-thrash-inactive.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-snb4/igt@gem_persistent_relocs@forked-thrash-inactive.html
- shard-hsw: [INCOMPLETE][16] ([i915#530] / [i915#61]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-hsw6/igt@gem_persistent_relocs@forked-thrash-inactive.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-hsw4/igt@gem_persistent_relocs@forked-thrash-inactive.html
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][18] ([i915#644]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-glk5/igt@gem_ppgtt@flink-and-close-vma-leak.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-glk9/igt@gem_ppgtt@flink-and-close-vma-leak.html
- shard-apl: [FAIL][20] ([i915#644]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-apl3/igt@gem_ppgtt@flink-and-close-vma-leak.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-apl3/igt@gem_ppgtt@flink-and-close-vma-leak.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-snb: [DMESG-WARN][22] ([fdo#111870]) -> [PASS][23] +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-snb2/igt@gem_userptr_blits@sync-unmap-cycles.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-snb4/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@i915_selftest@live_blt:
- shard-hsw: [DMESG-FAIL][24] ([i915#553]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-hsw7/igt@i915_selftest@live_blt.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-hsw4/igt@i915_selftest@live_blt.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-snb: [DMESG-WARN][26] ([i915#42]) -> [PASS][27]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-snb4/igt@kms_flip@flip-vs-suspend-interruptible.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-snb4/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-apl: [FAIL][28] ([i915#49]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7480/shard-apl8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/shard-apl7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#42]: https://gitlab.freedesktop.org/drm/intel/issues/42
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
[i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#675]: https://gitlab.freedesktop.org/drm/intel/issues/675
[i915#676]: https://gitlab.freedesktop.org/drm/intel/issues/676
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (11 -> 8)
------------------------------
Missing (3): pig-skl-6260u pig-glk-j5005 pig-hsw-4770r
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5323 -> IGTPW_3803
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_7480: acd4664d865fde46dcd32c48ccac1b048b355bea @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3803: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/index.html
IGT_5323: b0f877d06a78b9c38ed246be2537a0453b6c214f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3803/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-12-04 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:06 [igt-dev] [PATCH i-g-t] lib/ioctl_wrappers: Remove static variables for getting params Zbigniew Kempczyński
2019-12-04 8:18 ` Chris Wilson
2019-12-04 8:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-04 15:03 ` Patchwork [this message]
2019-12-06 12:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " Zbigniew Kempczyński
2019-12-09 7:13 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=157547178237.12194.2569602359543035344@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@intel.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 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.