From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/userptr: Never allow userptr into the mappable GGTT (rev3)
Date: Tue, 01 Oct 2019 10:06:44 -0000 [thread overview]
Message-ID: <20191001100644.21993.99984@emeril.freedesktop.org> (raw)
In-Reply-To: <20190927163400.22767-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/userptr: Never allow userptr into the mappable GGTT (rev3)
URL : https://patchwork.freedesktop.org/series/67349/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6980 -> Patchwork_14601
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_14601:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_sync@basic-many-each:
- {fi-cml-h}: NOTRUN -> [TIMEOUT][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-cml-h/igt@gem_sync@basic-many-each.html
* igt@runner@aborted:
- {fi-cml-h}: NOTRUN -> [FAIL][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-cml-h/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_14601 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@legacy-render:
- fi-icl-u2: [PASS][3] -> [INCOMPLETE][4] ([fdo#107713] / [fdo#111381])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u2/igt@gem_ctx_switch@legacy-render.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u2/igt@gem_ctx_switch@legacy-render.html
* igt@kms_addfb_basic@addfb25-yf-tiled:
- fi-icl-u3: [PASS][5] -> [DMESG-WARN][6] ([fdo#107724])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u3/igt@kms_addfb_basic@addfb25-yf-tiled.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u3/igt@kms_addfb_basic@addfb25-yf-tiled.html
* igt@kms_flip@basic-flip-vs-modeset:
- fi-hsw-4770r: [PASS][7] -> [DMESG-WARN][8] ([fdo#105602])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-hsw-4770r/igt@kms_flip@basic-flip-vs-modeset.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-hsw-4770r/igt@kms_flip@basic-flip-vs-modeset.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u3: [PASS][9] -> [FAIL][10] ([fdo#103167])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@gem_exec_fence@nb-await-default:
- fi-icl-u3: [DMESG-WARN][11] ([fdo#107724]) -> [PASS][12] +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u3/igt@gem_exec_fence@nb-await-default.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u3/igt@gem_exec_fence@nb-await-default.html
* igt@gem_sync@basic-each:
- {fi-tgl-u2}: [INCOMPLETE][13] ([fdo#111647]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-tgl-u2/igt@gem_sync@basic-each.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-tgl-u2/igt@gem_sync@basic-each.html
* igt@kms_frontbuffer_tracking@basic:
- {fi-icl-u4}: [FAIL][15] ([fdo#103167]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u4/igt@kms_frontbuffer_tracking@basic.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u4/igt@kms_frontbuffer_tracking@basic.html
- fi-hsw-peppy: [DMESG-WARN][17] ([fdo#102614]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
#### Warnings ####
* igt@i915_module_load@reload:
- fi-icl-u3: [DMESG-WARN][19] ([fdo#106107] / [fdo#107724] / [fdo#111214]) -> [DMESG-WARN][20] ([fdo#107724] / [fdo#111214])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6980/fi-icl-u3/igt@i915_module_load@reload.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/fi-icl-u3/igt@i915_module_load@reload.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#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#111214]: https://bugs.freedesktop.org/show_bug.cgi?id=111214
[fdo#111381]: https://bugs.freedesktop.org/show_bug.cgi?id=111381
[fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600
[fdo#111647]: https://bugs.freedesktop.org/show_bug.cgi?id=111647
Participating hosts (50 -> 44)
------------------------------
Additional (3): fi-byt-j1900 fi-cml-h fi-snb-2600
Missing (9): fi-ilk-m540 fi-bxt-dsi fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7500u fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6980 -> Patchwork_14601
CI-20190529: 20190529
CI_DRM_6980: 46637a3b58ef5e2c0fb6e53b7c50bba8f5de3455 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5208: c0131b4f132acf287d9d05b0f5078003d3159e1c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14601: d0541b40d6ed7753be10a3d766ddc97321e3f38f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
d0541b40d6ed drm/i915/userptr: Never allow userptr into the mappable GGTT
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14601/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-10-01 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 16:34 [PATCH] drm/i915/userptr: Never allow userptr into the mappable GGTT Chris Wilson
2019-09-27 16:42 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-09-27 17:05 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-28 8:05 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-09-28 8:25 ` [PATCH v2] " Chris Wilson
2019-09-30 10:33 ` [Intel-gfx] " Tvrtko Ursulin
2019-09-30 11:17 ` Chris Wilson
2019-09-28 8:35 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/userptr: Never allow userptr into the mappable GGTT (rev2) Patchwork
2019-09-28 9:25 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-28 19:13 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-09-28 20:03 ` [PATCH] drm/i915/userptr: Never allow userptr into the mappable GGTT Sasha Levin
2019-10-01 9:39 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/userptr: Never allow userptr into the mappable GGTT (rev3) Patchwork
2019-10-01 10:06 ` Patchwork [this message]
2019-10-01 13:40 ` ✗ Fi.CI.IGT: failure " 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=20191001100644.21993.99984@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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