All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for igt/gem_eio: Measure reset delay from thread
Date: Fri, 27 Jul 2018 16:16:32 +0100	[thread overview]
Message-ID: <153270459195.12384.14238203578878877290@skylake-alporthouse-com> (raw)
In-Reply-To: <20180727145237.31052.85201@emeril.freedesktop.org>

Quoting Patchwork (2018-07-27 15:52:37)
> == Series Details ==
> 
> Series: igt/gem_eio: Measure reset delay from thread
> URL   : https://patchwork.freedesktop.org/series/47338/
> State : failure
> 
> == Summary ==
> 
> = CI Bug Log - changes from IGT_4576_full -> IGTPW_1662_full =
> 
> == Summary - FAILURE ==
> 
>   Serious unknown changes coming with IGTPW_1662_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_1662_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://patchwork.freedesktop.org/api/1.0/series/47338/revisions/1/mbox/
> 
> == Possible new issues ==
> 
>   Here are the unknown changes that may have been introduced in IGTPW_1662_full:
> 
>   === IGT changes ===
> 
>     ==== Possible regressions ====
> 
>     igt@gem_eio@reset-stress:
>       shard-hsw:          PASS -> FAIL +2
> 
>     igt@gem_eio@wait-10ms:
>       shard-snb:          PASS -> FAIL
> 
>     
>     ==== Warnings ====
> 
>     igt@perf_pmu@rc6:
>       shard-kbl:          PASS -> SKIP
> 
>     
> == Known issues ==
> 
>   Here are the changes found in IGTPW_1662_full that come from known issues:
> 
>   === IGT changes ===
> 
>     ==== Issues hit ====
> 
>     igt@kms_cursor_crc@cursor-256x256-suspend:
>       shard-apl:          PASS -> FAIL (fdo#103375)
> 
>     igt@kms_cursor_crc@cursor-64x64-suspend:
>       shard-snb:          PASS -> INCOMPLETE (fdo#105411) +1
> 
>     igt@pm_rpm@modeset-non-lpsp-stress:
>       shard-kbl:          PASS -> FAIL (fdo#106539)
>       shard-hsw:          PASS -> FAIL (fdo#106539)
>       shard-glk:          PASS -> FAIL (fdo#106539)
>       shard-apl:          PASS -> FAIL (fdo#106539)

Hmm, eye opening. We've found a genuine bug, missing the wakeup.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-07-27 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 11:13 [PATCH i-g-t] igt/gem_eio: Measure reset delay from thread Chris Wilson
2018-07-27 11:13 ` [igt-dev] " Chris Wilson
2018-07-27 13:24 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-07-27 14:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-07-27 15:16   ` Chris Wilson [this message]
2018-07-27 18:44     ` Chris Wilson
2018-07-30 16:20 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-07-30 18:29 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-07-30 18:33   ` Chris Wilson
2018-08-03 14:03 ` [igt-dev] [PATCH i-g-t] " Tvrtko Ursulin
2018-08-03 14:03   ` Tvrtko Ursulin
2018-08-03 14:10   ` Chris Wilson
2018-08-03 14:10     ` Chris Wilson

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=153270459195.12384.14238203578878877290@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=patchwork@emeril.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.