From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for lib: Purge os caches twice for good luck
Date: Sun, 17 Jun 2018 12:01:29 -0000 [thread overview]
Message-ID: <20180617120129.20235.79023@emeril.freedesktop.org> (raw)
In-Reply-To: <20180615133249.3505-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: lib: Purge os caches twice for good luck
URL : https://patchwork.freedesktop.org/series/44832/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4329 -> IGTPW_1473 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/44832/revisions/1/mbox/
== Known issues ==
Here are the changes found in IGTPW_1473 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_module_reload@basic-reload-inject:
fi-glk-j4005: NOTRUN -> DMESG-WARN (fdo#106248, fdo#106725) +1
igt@kms_flip@basic-flip-vs-wf_vblank:
fi-cnl-psr: PASS -> FAIL (fdo#100368)
fi-glk-j4005: NOTRUN -> FAIL (fdo#100368)
igt@prime_vgem@basic-fence-flip:
fi-ilk-650: PASS -> FAIL (fdo#104008)
==== Possible fixes ====
igt@gem_exec_gttfill@basic:
fi-byt-n2820: FAIL (fdo#106744) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-skl-6260u: INCOMPLETE (fdo#104108) -> PASS
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
fdo#104108 https://bugs.freedesktop.org/show_bug.cgi?id=104108
fdo#106248 https://bugs.freedesktop.org/show_bug.cgi?id=106248
fdo#106725 https://bugs.freedesktop.org/show_bug.cgi?id=106725
fdo#106744 https://bugs.freedesktop.org/show_bug.cgi?id=106744
== Participating hosts (42 -> 37) ==
Additional (1): fi-glk-j4005
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-kbl-r
== Build changes ==
* IGT: IGT_4521 -> IGTPW_1473
CI_DRM_4329: 02d8db1a894b0e646b2debd64ce24b8e99fd2ffd @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_1473: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1473/
IGT_4521: 4aa49a88acdaafed8235837d85a099ad941fc281 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1473/issues.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-06-17 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 13:32 [igt-dev] [PATCH i-g-t] lib: Purge os caches twice for good luck Chris Wilson
2018-06-15 15:31 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-06-16 1:04 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-06-16 18:19 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2018-06-16 19:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-06-16 20:42 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2018-06-16 21:34 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-06-17 12:01 ` Patchwork [this message]
2018-06-17 12:56 ` Patchwork
2018-06-17 18:51 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2018-06-17 19:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-06-18 8:06 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2018-06-18 8:58 ` Joonas Lahtinen
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=20180617120129.20235.79023@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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