public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/i915/query: Test invalid TOPO_INFO flags
Date: Fri, 21 Jun 2019 22:18:47 +0000	[thread overview]
Message-ID: <3db5b335feed8ec7d13ca271a63bb156e0549375.camel@intel.com> (raw)
In-Reply-To: <20190621194834.9266.32909@emeril.freedesktop.org>


[-- Attachment #1.1: Type: text/plain, Size: 2186 bytes --]

On Fri, 2019-06-21 at 19:48 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: tests/i915/query: Test invalid TOPO_INFO flags
> URL   : https://patchwork.freedesktop.org/series/62552/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_6327 -> IGTPW_3188
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3188 absolutely need to
> be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the
> changes
>   introduced in IGTPW_3188, 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/62552/revisions/1/mbox/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in
> IGTPW_3188:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@runner@aborted:
>     - fi-gdg-551:         NOTRUN -> [FAIL][1]
>    [1]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3188/fi-gdg-551/igt@runner@aborted.html

Seems like something new/unrelated?
<7>[   80.892026] [drm:vgem_gem_dumb_create [vgem]] Created object of
size 1
<1>[   80.892056] BUG: kernel NULL pointer dereference, address:
0000000000000000

Thanks,
Stuart

> 
>   
> 
> 
> Participating hosts (50 -> 43)
> ------------------------------
> 
>   Additional (1): fi-gdg-551 
>   Missing    (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-
> squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus 
> 
> 
> Build changes
> -------------
> 
>   * IGT: IGT_5064 -> IGTPW_3188
> 
>   CI_DRM_6327: d2ee3427319b7e89e9ab49c8e4b714789b611dfe @
> git://anongit.freedesktop.org/gfx-ci/linux
>   IGTPW_3188: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3188/
>   IGT_5064: 22850c1906550fb97b405c019275dcfb34be8cf7 @
> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> 
> == Logs ==
> 
> For more details see: 
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3188/

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-06-21 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 19:15 [igt-dev] [PATCH i-g-t] tests/i915/query: Test invalid TOPO_INFO flags Stuart Summers
2019-06-21 19:48 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-21 22:18   ` Summers, Stuart [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=3db5b335feed8ec7d13ca271a63bb156e0549375.camel@intel.com \
    --to=stuart.summers@intel.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