From: John Harrison <John.C.Harrison@Intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Update to GuC FW v40 (rev3)
Date: Thu, 23 Jan 2020 13:35:15 -0800 [thread overview]
Message-ID: <beb5514c-37ec-e199-4353-245c7ebe2662@Intel.com> (raw)
In-Reply-To: <157974624624.1146.4619213646517580934@emeril.freedesktop.org>
[-- Attachment #1.1: Type: text/plain, Size: 2301 bytes --]
On 1/22/2020 18:24, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Update to GuC FW v40 (rev3)
> URL : https://patchwork.freedesktop.org/series/72032/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7786_full -> Patchwork_16198_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16198_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16198_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_16198_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_atomic_transition@5x-modeset-transitions-fencing:
> - shard-tglb: NOTRUN -> [SKIP][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16198/shard-tglb8/igt@kms_atomic_transition@5x-modeset-transitions-fencing.html
According to the log, this test failed because it ran on a device that
only had one display device attached and not the five required by the test:
IGT-Version: 1.24-g5cf58d947 (x86_64) (Linux: 5.5.0-rc7-CI-Patchwork_16198+ x86_64)
Starting subtest: 5x-modeset-transitions-fencing
Test requirement not met in function run_modeset_transition, file ../tests/kms_atomic_transition.c:887:
Test requirement: num_outputs >= requested_outputs
Should have at least 5 outputs, found 1
Subtest 5x-modeset-transitions-fencing: SKIP (0.000s)
I'm not sure how that could be called a regression in the GuC FW patch.
I also don't see any reason why the test would previously have been a
'NOTRUN' and now is being attempted. Changing the GuC FW should not
affect which KMS tests do or do not get run!
I don't have a system with five display devices so I can't actually run
the test myself either. However, I do not see how this could be affected
by changes to the GuC. Especially when the GuC is only being used for
HuC authentication.
So I think this definitely counts as an issue with CI not this patch.
John.
[-- Attachment #1.2: Type: text/html, Size: 3887 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-23 21:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 2:40 [Intel-gfx] [PATCH] drm/i915/guc: Update to GuC FW v40 John.C.Harrison
2020-01-15 3:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-15 3:24 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-15 19:45 ` [Intel-gfx] [PATCH] " Daniele Ceraolo Spurio
2020-01-15 19:49 ` John Harrison
2020-01-15 20:37 ` [Intel-gfx] [PATCH v2] " John.C.Harrison
2020-01-21 18:29 ` Daniele Ceraolo Spurio
2020-01-21 18:40 ` John Harrison
2020-01-15 21:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Update to GuC FW v40 (rev2) Patchwork
2020-01-15 21:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-17 10:12 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Update to GuC FW v40 Patchwork
2020-01-18 9:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Update to GuC FW v40 (rev2) Patchwork
2020-01-21 19:09 ` [Intel-gfx] [CI v2 1/2] drm/i915/guc: Update to GuC FW v40 John.C.Harrison
2020-01-21 19:09 ` [Intel-gfx] [CI v2 2/2] Hack for CI: enable HuC loading by default John.C.Harrison
2020-01-21 19:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update to GuC FW v40 (rev3) Patchwork
2020-01-21 20:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-23 2:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-01-23 21:35 ` John Harrison [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=beb5514c-37ec-e199-4353-245c7ebe2662@Intel.com \
--to=john.c.harrison@intel.com \
--cc=intel-gfx@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;
as well as URLs for NNTP newsgroup(s).