public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org,
	Arkadiusz Hiler <arkadiusz.hiler@intel.com>,
	Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for i915/gem_exec_basic: Use dynamic subtests
Date: Thu, 9 Jan 2020 12:35:46 +0200	[thread overview]
Message-ID: <20200109103546.GK25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <157850320337.23226.8646134144920356374@emeril.freedesktop.org>

On Wed, Jan 08, 2020 at 05:06:43PM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: i915/gem_exec_basic: Use dynamic subtests
> URL   : https://patchwork.freedesktop.org/series/71733/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_7699_full -> IGTPW_3904_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3904_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_3904_full, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3904/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_3904_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_busy@close-race:
>     - shard-hsw:          NOTRUN -> [TIMEOUT][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3904/shard-hsw1/igt@gem_busy@close-race.html
> 
>   * igt@gem_eio@kms:
>     - shard-hsw:          [PASS][2] -> [DMESG-WARN][3]
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7699/shard-hsw2/igt@gem_eio@kms.html
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3904/shard-hsw5/igt@gem_eio@kms.html


Lakshmi, some false positives for you above.




> 
>   
> New tests
> ---------
> 
>   New tests have been introduced between CI_DRM_7699_full and IGTPW_3904_full:
> 
> ### New IGT tests (18) ###
> 
>   * igt@gem_exec_basic@basic:
>     - Statuses : 1 pass(s)
>     - Exec time: [0.00] s

I was wondering where the heck this came from (it's the base subtest,
and should not be reported) but the shard round this was in was
incomplete and the report generation was done with an older IGT.

Arek, wasn't updating the report-generating-IGT made automatic on
post-merge? It hasn't happened for this report.



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

      reply	other threads:[~2020-01-09 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  5:34 [igt-dev] [PATCH i-g-t v2] i915/gem_exec_basic: Use dynamic subtests Petri Latvala
2020-01-08  5:49 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-01-08  6:04 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-01-08 12:22 ` [igt-dev] [PATCH i-g-t v2] " Katarzyna Dec
2020-01-08 17:06 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2020-01-09 10:35   ` Petri Latvala [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=20200109103546.GK25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lakshminarayana.vudum@intel.com \
    /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