From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/gem_exec_async: Update with engine discovery
Date: Wed, 24 Jul 2019 10:23:53 -0000 [thread overview]
Message-ID: <20190724102353.10331.9559@emeril.freedesktop.org> (raw)
In-Reply-To: <20190724022118.26136-1-ramalingam.c@intel.com>
== Series Details ==
Series: tests/i915/gem_exec_async: Update with engine discovery
URL : https://patchwork.freedesktop.org/series/64162/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6544 -> IGTPW_3290
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/64162/revisions/1/mbox/
Known issues
------------
Here are the changes found in IGTPW_3290 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap_gtt@basic-wc:
- fi-bsw-kefka: [PASS][1] -> [FAIL][2] ([fdo#107307])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-bsw-kefka/igt@gem_mmap_gtt@basic-wc.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-bsw-kefka/igt@gem_mmap_gtt@basic-wc.html
* igt@i915_module_load@reload-no-display:
- fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-icl-u3/igt@i915_module_load@reload-no-display.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-icl-u3/igt@i915_module_load@reload-no-display.html
* igt@kms_busy@basic-flip-a:
- fi-kbl-7567u: [PASS][5] -> [SKIP][6] ([fdo#109271] / [fdo#109278]) +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7567u: [PASS][7] -> [WARN][8] ([fdo#109380])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-kbl-7567u/igt@kms_chamelium@common-hpd-after-suspend.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-kbl-7567u/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][9] -> [FAIL][10] ([fdo#109485])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: [PASS][11] -> [DMESG-WARN][12] ([fdo#102614])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
- fi-icl-u2: [PASS][13] -> [FAIL][14] ([fdo#103167])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- fi-kbl-7567u: [PASS][15] -> [SKIP][16] ([fdo#109271]) +23 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-kbl-7567u/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-kbl-7567u/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-ilk-650: [DMESG-WARN][17] ([fdo#106387]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-ilk-650/igt@debugfs_test@read_all_entries.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-ilk-650/igt@debugfs_test@read_all_entries.html
* igt@gem_mmap_gtt@basic-write-gtt:
- fi-icl-u3: [DMESG-WARN][19] ([fdo#107724]) -> [PASS][20] +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-icl-u3/igt@gem_mmap_gtt@basic-write-gtt.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-icl-u3/igt@gem_mmap_gtt@basic-write-gtt.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u3: [FAIL][21] ([fdo#103167]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#106387]: https://bugs.freedesktop.org/show_bug.cgi?id=106387
[fdo#107307]: https://bugs.freedesktop.org/show_bug.cgi?id=107307
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109380]: https://bugs.freedesktop.org/show_bug.cgi?id=109380
[fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
Participating hosts (52 -> 44)
------------------------------
Additional (1): fi-cfl-8109u
Missing (9): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-guc fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5109 -> IGTPW_3290
CI-20190529: 20190529
CI_DRM_6544: 067ab13ae8bd0a5deb5283344664ab929839d56e @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3290: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/
IGT_5109: e5fd509e16ec649436be31f38eaa5b85cb7f72f1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Testlist changes ==
+igt@gem_exec_async@concurrent-writes-bcs0
+igt@gem_exec_async@concurrent-writes-rcs0
+igt@gem_exec_async@concurrent-writes-vcs0
+igt@gem_exec_async@concurrent-writes-vcs1
+igt@gem_exec_async@concurrent-writes-vcs2
+igt@gem_exec_async@concurrent-writes-vecs0
+igt@gem_exec_async@legacy-concurrent-writes-bcs0
+igt@gem_exec_async@legacy-concurrent-writes-default
+igt@gem_exec_async@legacy-concurrent-writes-rcs0
+igt@gem_exec_async@legacy-concurrent-writes-vcs0
+igt@gem_exec_async@legacy-concurrent-writes-vcs1
+igt@gem_exec_async@legacy-concurrent-writes-vecs0
-igt@gem_exec_async@concurrent-writes-blt
-igt@gem_exec_async@concurrent-writes-bsd
-igt@gem_exec_async@concurrent-writes-bsd1
-igt@gem_exec_async@concurrent-writes-bsd2
-igt@gem_exec_async@concurrent-writes-render
-igt@gem_exec_async@concurrent-writes-vebox
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3290/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-07-24 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 2:21 [igt-dev] [PATCH i-g-t] tests/i915/gem_exec_async: Update with engine discovery Ramalingam C
2019-07-24 10:23 ` Patchwork [this message]
2019-07-24 10:28 ` Chris Wilson
2019-07-24 8:30 ` Ramalingam C
2019-07-24 13:10 ` Tvrtko Ursulin
2019-07-24 8:34 ` Ramalingam C
2019-07-24 14:17 ` [igt-dev] ✓ Fi.CI.IGT: 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=20190724102353.10331.9559@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramalingam.c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox