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
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for runner: add --list-all and --blacklist (rev4)
Date: Tue, 18 Jun 2019 12:41:30 +0300	[thread overview]
Message-ID: <20190618094130.GY22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190618093620.30452.13198@emeril.freedesktop.org>

On Tue, Jun 18, 2019 at 09:36:20AM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: runner: add --list-all and --blacklist (rev4)
> URL   : https://patchwork.freedesktop.org/series/62106/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_6290 -> IGTPW_3168
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3168 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_3168, 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/62106/revisions/4/mbox/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_3168:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_suspend@basic-s3:
>     - fi-cfl-guc:         [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6290/fi-cfl-guc/igt@gem_exec_suspend@basic-s3.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3168/fi-cfl-guc/igt@gem_exec_suspend@basic-s3.html
> 
>   * igt@runner@aborted:
>     - fi-cfl-guc:         NOTRUN -> [FAIL][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3168/fi-cfl-guc/igt@runner@aborted.html


CC Martin

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

  reply	other threads:[~2019-06-18  9:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 13:24 [igt-dev] [PATCH] runner: add --list-all and --blacklist Oleg Vasilev
2019-06-14 13:43 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-14 14:28 ` [igt-dev] [PATCH] " Petri Latvala
2019-06-17 11:49 ` [igt-dev] [PATCH v2] " Oleg Vasilev
2019-06-17 12:41   ` Petri Latvala
2019-06-17 13:41   ` [igt-dev] [PATCH v3] " Oleg Vasilev
2019-06-18  8:11     ` Petri Latvala
2019-06-18  9:07       ` [igt-dev] [PATCH v4] " Oleg Vasilev
2019-06-18  9:26         ` Petri Latvala
2019-06-17 14:14 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: add --list-all and --blacklist (rev2) Patchwork
2019-06-17 15:31 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: add --list-all and --blacklist (rev3) Patchwork
2019-06-17 23:23 ` [igt-dev] ✓ Fi.CI.IGT: success for runner: add --list-all and --blacklist (rev2) Patchwork
2019-06-18  2:11 ` [igt-dev] ✓ Fi.CI.IGT: success for runner: add --list-all and --blacklist (rev3) Patchwork
2019-06-18  9:36 ` [igt-dev] ✗ Fi.CI.BAT: failure for runner: add --list-all and --blacklist (rev4) Patchwork
2019-06-18  9:41   ` Petri Latvala [this message]
2019-06-18 10:39 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-06-18 20:05 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190618094130.GY22949@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