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 runner: Flip kill args
Date: Tue, 27 Nov 2018 14:05:07 -0000 [thread overview]
Message-ID: <20181127140507.13466.29618@emeril.freedesktop.org> (raw)
In-Reply-To: <20181127122255.11566-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: runner: Flip kill args
URL : https://patchwork.freedesktop.org/series/53077/
State : success
== Summary ==
= CI Bug Log - changes from IGT_4730 -> IGTPW_2100 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/53077/revisions/1/mbox/
== Known issues ==
Here are the changes found in IGTPW_2100 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_suspend@basic-s3:
fi-cfl-8109u: NOTRUN -> INCOMPLETE (fdo#107187, fdo#108126)
igt@gem_exec_suspend@basic-s4-devices:
fi-ivb-3520m: PASS -> FAIL (fdo#108880)
igt@kms_frontbuffer_tracking@basic:
{fi-icl-u3}: PASS -> FAIL (fdo#103167)
fi-byt-clapper: PASS -> FAIL (fdo#103167)
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b:
fi-byt-clapper: PASS -> FAIL (fdo#107362) +1
==== Possible fixes ====
igt@gem_exec_suspend@basic-s3:
fi-blb-e6850: INCOMPLETE (fdo#107718) -> PASS
igt@i915_selftest@live_contexts:
fi-bsw-kefka: DMESG-FAIL (fdo#108656, fdo#108626) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#107187 https://bugs.freedesktop.org/show_bug.cgi?id=107187
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
fdo#108126 https://bugs.freedesktop.org/show_bug.cgi?id=108126
fdo#108626 https://bugs.freedesktop.org/show_bug.cgi?id=108626
fdo#108656 https://bugs.freedesktop.org/show_bug.cgi?id=108656
fdo#108880 https://bugs.freedesktop.org/show_bug.cgi?id=108880
== Participating hosts (50 -> 46) ==
Additional (2): fi-cfl-8109u fi-pnv-d510
Missing (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600
== Build changes ==
* IGT: IGT_4730 -> IGTPW_2100
CI_DRM_5208: e556a1602bef92792a069e4fe1cb2c851efb2294 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_2100: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2100/
IGT_4730: a6b514d242bddd9457f04bb25cde0ddf85032b65 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2100/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-11-27 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 12:22 [igt-dev] [PATCH i-g-t] runner: Flip kill args Chris Wilson
2018-11-27 12:42 ` Petri Latvala
2018-11-27 12:52 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2018-11-27 14:05 ` Patchwork [this message]
2018-11-27 15:55 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=20181127140507.13466.29618@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