From: Patchwork <patchwork@emeril.freedesktop.org>
To: Vanshidhar Konda <vanshidhar.r.konda@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_spin_batch: Add test to execute in parallel on all engines
Date: Thu, 31 Oct 2019 18:43:22 -0000 [thread overview]
Message-ID: <20191031184322.29575.93997@emeril.freedesktop.org> (raw)
In-Reply-To: <20191031180159.815665-1-vanshidhar.r.konda@intel.com>
== Series Details ==
Series: i915/gem_spin_batch: Add test to execute in parallel on all engines
URL : https://patchwork.freedesktop.org/series/68834/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7233 -> IGTPW_3639
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3639/index.html
Known issues
------------
Here are the changes found in IGTPW_3639 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap@basic:
- fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7233/fi-icl-u3/igt@gem_mmap@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3639/fi-icl-u3/igt@gem_mmap@basic.html
#### Possible fixes ####
* igt@gem_mmap_gtt@basic-small-bo-tiledy:
- fi-icl-u3: [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7233/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledy.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3639/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledy.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#112096]: https://bugs.freedesktop.org/show_bug.cgi?id=112096
Participating hosts (53 -> 45)
------------------------------
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-tgl-u2 fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5255 -> IGTPW_3639
CI-20190529: 20190529
CI_DRM_7233: 1cdd3a3d9f5a2b0e0879d0d2468d4c88efdcda4f @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3639: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3639/index.html
IGT_5255: b21b6a7aaa0db2159f22ee4427804e5a16fe2261 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Testlist changes ==
+igt@gem_spin_batch@spin-all-parallel
+igt@gem_spin_batch@spin-all-parallel-new-ctx
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3639/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-10-31 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191031180159.815665-1-vanshidhar.r.konda@intel.com>
2019-10-31 18:17 ` [igt-dev] [PATCH] i915/gem_spin_batch: Add test to execute in parallel on all engines Chris Wilson
2019-10-31 18:28 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2019-10-31 18:43 ` Patchwork [this message]
2019-10-31 21:55 ` [igt-dev] [PATCH] " Chris Wilson
2019-11-01 23:57 ` [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=20191031184322.29575.93997@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=vanshidhar.r.konda@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