From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/selftests: Fix an IS_ERR() vs NULL check (rev3)
Date: Thu, 28 Mar 2019 13:56:25 +0200 [thread overview]
Message-ID: <87ftr7yzyu.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190327132417.22542.71506@emeril.freedesktop.org>
Patchwork <patchwork@emeril.freedesktop.org> writes:
> == Series Details ==
>
> Series: drm/i915/selftests: Fix an IS_ERR() vs NULL check (rev3)
Ok, never ever send a patch with identical subject line.
> URL : https://patchwork.freedesktop.org/series/58557/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5824 -> Patchwork_12612
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_12612 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_12612, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> External URL: https://patchwork.freedesktop.org/api/1.0/series/58557/revisions/3/mbox/
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_12612:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live_uncore:
> - fi-kbl-8809g: PASS -> DMESG-FAIL
<3> [320.015575] bcs0:RING_MI_MODE=200, fw_domains 0x2 still up after 100ms!
-Mika
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_12612 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_exec_basic@readonly-bsd2:
> - fi-pnv-d510: NOTRUN -> SKIP [fdo#109271] +76
>
> * igt@i915_selftest@live_contexts:
> - fi-skl-gvtdvm: PASS -> DMESG-FAIL [fdo#110235 ]
>
> * igt@kms_busy@basic-flip-c:
> - fi-pnv-d510: NOTRUN -> SKIP [fdo#109271] / [fdo#109278]
>
> * igt@kms_frontbuffer_tracking@basic:
> - fi-byt-clapper: PASS -> FAIL [fdo#103167]
>
> * igt@prime_vgem@basic-fence-flip:
> - fi-gdg-551: PASS -> FAIL [fdo#103182]
>
>
> #### Possible fixes ####
>
> * igt@kms_busy@basic-flip-a:
> - fi-gdg-551: FAIL [fdo#103182] -> PASS
>
>
> [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
> [fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
> [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
> [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
> [fdo#110235 ]: https://bugs.freedesktop.org/show_bug.cgi?id=110235
>
>
> Participating hosts (42 -> 37)
> ------------------------------
>
> Additional (1): fi-pnv-d510
> Missing (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-bdw-samus
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_5824 -> Patchwork_12612
>
> CI_DRM_5824: d6a239f8bd502261971e5a2fb0ec71ae0b30b298 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_4907: 7c8f2616fa0fd3ddb16e050c5b7ea9ce707abbe4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_12612: 545ca65d2548ce9a6d6c965abb1ce061d2c7eb18 @ git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Linux commits ==
>
> 545ca65d2548 drm/i915/selftests: Fix an IS_ERR() vs NULL check
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12612/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-03-28 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 9:20 [PATCH] drm/i915/selftests: Fix an IS_ERR() vs NULL check Mika Kuoppala
2019-03-27 9:25 ` Chris Wilson
2019-03-27 9:32 ` Mika Kuoppala
2019-03-27 9:52 ` Chris Wilson
2019-03-27 13:24 ` ✗ Fi.CI.BAT: failure for drm/i915/selftests: Fix an IS_ERR() vs NULL check (rev3) Patchwork
2019-03-28 11:56 ` Mika Kuoppala [this message]
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=87ftr7yzyu.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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