From: Patchwork <patchwork@emeril.freedesktop.org>
To: Oleg Vasilev <oleg.vasilev@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] gitlab-ci: move containers section to the up
Date: Tue, 20 Aug 2019 16:08:17 -0000 [thread overview]
Message-ID: <20190820160817.30810.72091@emeril.freedesktop.org> (raw)
In-Reply-To: <20190820131936.25640-1-oleg.vasilev@intel.com>
== Series Details ==
Series: series starting with [v2,1/3] gitlab-ci: move containers section to the up
URL : https://patchwork.freedesktop.org/series/65480/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6745 -> IGTPW_3368
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/65480/revisions/1/mbox/
Known issues
------------
Here are the changes found in IGTPW_3368 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@legacy-render:
- fi-bxt-dsi: [PASS][1] -> [INCOMPLETE][2] ([fdo#103927])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-bxt-dsi/igt@gem_ctx_switch@legacy-render.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-bxt-dsi/igt@gem_ctx_switch@legacy-render.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u2: [PASS][3] -> [FAIL][4] ([fdo#103167])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@gem_sync@basic-store-each:
- fi-cfl-8109u: [INCOMPLETE][5] ([fdo#111427]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-cfl-8109u/igt@gem_sync@basic-store-each.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-cfl-8109u/igt@gem_sync@basic-store-each.html
* {igt@i915_selftest@live_gt_timelines}:
- fi-bsw-kefka: [DMESG-WARN][7] ([fdo#111373]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-bsw-kefka/igt@i915_selftest@live_gt_timelines.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-bsw-kefka/igt@i915_selftest@live_gt_timelines.html
* igt@kms_busy@basic-flip-a:
- fi-kbl-7567u: [SKIP][9] ([fdo#109271] / [fdo#109278]) -> [PASS][10] +2 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: [DMESG-WARN][11] ([fdo#102614]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6745/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/fi-hsw-peppy/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#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#111373]: https://bugs.freedesktop.org/show_bug.cgi?id=111373
[fdo#111427]: https://bugs.freedesktop.org/show_bug.cgi?id=111427
Participating hosts (56 -> 47)
------------------------------
Missing (9): fi-kbl-soraka fi-ilk-m540 fi-tgl-u fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5145 -> IGTPW_3368
CI-20190529: 20190529
CI_DRM_6745: 001f02411223cb625aed43fbed5c1bbcecc447f7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3368: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/
IGT_5145: 50251bcb2e8783f86ebdd86ce38adc9e3777f82f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3368/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-08-20 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 13:19 [igt-dev] Add containers with IGT inside Oleg Vasilev
2019-08-20 13:19 ` [igt-dev] [PATCH v2 1/3] gitlab-ci: move containers section to the up Oleg Vasilev
2019-08-22 8:45 ` Arkadiusz Hiler
2019-08-20 13:19 ` [igt-dev] [PATCH v2 2/3] gitlab-ci: rebuild images only on Dockerfile changes Oleg Vasilev
2019-08-22 8:26 ` Arkadiusz Hiler
2019-08-20 13:19 ` [igt-dev] [PATCH v2 3/3] gitlab-ci: introduce final containers Oleg Vasilev
2019-08-22 8:45 ` Arkadiusz Hiler
2019-08-23 12:41 ` Vasilev, Oleg
2019-08-23 12:50 ` Arkadiusz Hiler
2019-08-23 12:56 ` Arkadiusz Hiler
2019-08-20 16:08 ` Patchwork [this message]
2019-08-20 23:48 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [v2,1/3] gitlab-ci: move containers section to the up 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=20190820160817.30810.72091@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=oleg.vasilev@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