public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for kms_cursor_legacy: Keep primary plane enabled for XRGB overlay fallback
Date: Mon, 8 Jun 2020 18:29:37 +0200	[thread overview]
Message-ID: <bf28cdb6-e5db-b3e5-3208-85fb56620efa@daenzer.net> (raw)
In-Reply-To: <159137452678.18506.1035039871677989119@emeril.freedesktop.org>

On 2020-06-05 6:28 p.m., Patchwork wrote:
> == Series Details ==
> 
> Series: kms_cursor_legacy: Keep primary plane enabled for XRGB overlay fallback
> URL   : https://patchwork.freedesktop.org/series/78047/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_8590_full -> IGTPW_4652_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_4652_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_4652_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_4652/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_4652_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_flush@basic-wb-ro-before-default:
>     - shard-hsw:          [PASS][1] -> [TIMEOUT][2] +2 similar issues
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw7/igt@gem_exec_flush@basic-wb-ro-before-default.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4652/shard-hsw5/igt@gem_exec_flush@basic-wb-ro-before-default.html
> 
>   * igt@gem_exec_reloc@basic-cpu-read-noreloc:
>     - shard-snb:          [PASS][3] -> [TIMEOUT][4] +2 similar issues
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb4/igt@gem_exec_reloc@basic-cpu-read-noreloc.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4652/shard-snb5/igt@gem_exec_reloc@basic-cpu-read-noreloc.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_ccs@pipe-d-missing-ccs-buffer:
>     - shard-snb:          [SKIP][5] ([fdo#109271]) -> [TIMEOUT][6] +1 similar issue
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb4/igt@kms_ccs@pipe-d-missing-ccs-buffer.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4652/shard-snb5/igt@kms_ccs@pipe-d-missing-ccs-buffer.html
>     - shard-hsw:          [SKIP][7] ([fdo#109271]) -> [TIMEOUT][8] +1 similar issue
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw4/igt@kms_ccs@pipe-d-missing-ccs-buffer.html
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4652/shard-hsw5/igt@kms_ccs@pipe-d-missing-ccs-buffer.html

None of these can be related to my patch, as it only affects the
*atomic-transitions* sub-tests of the kms_cursor_legacy test.


-- 
Earthling Michel Dänzer               |               https://redhat.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-06-08 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 14:37 [igt-dev] [PATCH] kms_cursor_legacy: Keep primary plane enabled for XRGB overlay fallback Michel Dänzer
2020-06-05 15:13 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-05 16:28 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-08 16:29   ` Michel Dänzer [this message]
2020-06-09 14:50 ` [igt-dev] [PATCH] " Ville Syrjälä
2020-06-09 16:40   ` Michel Dänzer
2020-06-09 16:49     ` Ville Syrjälä
2020-06-11  8:25 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-06-11  8:39   ` Michel Dänzer

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=bf28cdb6-e5db-b3e5-3208-85fb56620efa@daenzer.net \
    --to=michel@daenzer.net \
    --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