From: Patchwork <patchwork@emeril.freedesktop.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for gitlab-ci: add build for MIPS
Date: Wed, 05 Jun 2019 21:11:41 -0000 [thread overview]
Message-ID: <20190605211141.10844.19903@emeril.freedesktop.org> (raw)
In-Reply-To: <20190605201809.19657-1-guillaume.tucker@collabora.com>
== Series Details ==
Series: gitlab-ci: add build for MIPS
URL : https://patchwork.freedesktop.org/series/61689/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6198 -> IGTPW_3124
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/61689/revisions/1/mbox/
Known issues
------------
Here are the changes found in IGTPW_3124 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_workarounds@basic-read:
- fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6198/fi-icl-u3/igt@gem_workarounds@basic-read.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3124/fi-icl-u3/igt@gem_workarounds@basic-read.html
#### Possible fixes ####
* igt@core_auth@basic-auth:
- fi-icl-u3: [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4] +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6198/fi-icl-u3/igt@core_auth@basic-auth.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3124/fi-icl-u3/igt@core_auth@basic-auth.html
* igt@gem_ctx_switch@basic-default:
- {fi-icl-guc}: [INCOMPLETE][5] ([fdo#107713] / [fdo#108569]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6198/fi-icl-guc/igt@gem_ctx_switch@basic-default.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3124/fi-icl-guc/igt@gem_ctx_switch@basic-default.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[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
Participating hosts (52 -> 45)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7560u fi-byt-clapper fi-bdw-samus
Build changes
-------------
* IGT: IGT_5041 -> IGTPW_3124
CI_DRM_6198: 5550e8de34053c54224724c876cda34db56fc15c @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3124: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3124/
IGT_5041: 4f2b9f5930fa33d091cf89637dc6e7f76f632a88 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3124/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-05 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:18 [igt-dev] [PATCH i-g-t] gitlab-ci: add build for MIPS Guillaume Tucker
2019-06-05 21:11 ` Patchwork [this message]
2019-06-06 13:16 ` Arkadiusz Hiler
2019-06-13 13:09 ` Guillaume Tucker
2019-06-07 18:20 ` [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=20190605211141.10844.19903@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=guillaume.tucker@collabora.com \
--cc=igt-dev@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