From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] runner: Refactor timeouting
Date: Wed, 19 Feb 2020 12:39:21 +0200 [thread overview]
Message-ID: <20200219103921.GR25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <158209619321.21060.5167287093269139449@emeril.freedesktop.org>
On Wed, Feb 19, 2020 at 07:09:53AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [i-g-t,1/2] runner: Refactor timeouting
> URL : https://patchwork.freedesktop.org/series/73539/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7955_full -> IGTPW_4166_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_4166_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_4166_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_4166/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_4166_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_exec_suspend@basic-s3:
> - shard-iclb: NOTRUN -> [INCOMPLETE][1] +4 similar issues
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4166/shard-iclb1/igt@gem_exec_suspend@basic-s3.html
rc2 fallout, so merged.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2020-02-19 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 14:50 [igt-dev] [PATCH i-g-t 1/2] runner: Refactor timeouting Petri Latvala
2020-02-17 14:50 ` [igt-dev] [PATCH i-g-t 2/2] runner: Introduce per-test timeouts Petri Latvala
2020-02-18 10:24 ` Chris Wilson
2020-02-18 11:26 ` Petri Latvala
2020-02-17 16:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] runner: Refactor timeouting Patchwork
2020-02-18 11:29 ` Petri Latvala
2020-02-18 9:08 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2020-02-18 10:21 ` Chris Wilson
2020-02-18 15:38 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] " Patchwork
2020-02-19 7:09 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-02-19 10:39 ` 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=20200219103921.GR25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@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