Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for Fixes for i915_hangman and gem_exec_capture (rev6)
Date: Thu, 13 Jan 2022 14:53:55 -0800	[thread overview]
Message-ID: <20220113225354.GA27056@jons-linux-dev-box> (raw)
In-Reply-To: <164211260964.19001.14947415571214721339@emeril.freedesktop.org>

On Thu, Jan 13, 2022 at 10:23:29PM +0000, Patchwork wrote:
> Patch Details
> 
> Series:  Fixes for i915_hangman and gem_exec_capture (rev6)
> URL:     https://patchwork.freedesktop.org/series/97981/
> State:   failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6553/index.html
> 
> CI Bug Log - changes from CI_DRM_11080 -> IGTPW_6553
> 
> Summary
> 
> FAILURE
> 
> Serious unknown changes coming with IGTPW_6553 absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_6553, 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_6553/index.html
> 
> Participating hosts (41 -> 41)
> 
> Additional (1): fi-kbl-soraka
> Missing (1): fi-bsw-cyan
> 
> Possible new issues
> 
> Here are the unknown changes that may have been introduced in IGTPW_6553:
> 
> IGT changes
> 
> Possible regressions
> 
>   • igt@i915_hangman@error-state-basic:
>       □ bat-dg1-6: PASS -> SKIP

It looks like it is skipped because of the requirement:
Test requirement not met in function __igt_unique____real_main495, file ../tests/i915/i915_hangman.c:517:
Test requirement: gem_mmap__has_wc(device)

Which was added in this patch:
https://patchwork.freedesktop.org/patch/469465/?series=97981&rev=6

 static void do_tests(const char *name, const char *prefix,
@@ -433,6 +490,8 @@  igt_main
 		igt_assert(sysfs != -1);
 
 		igt_require(has_error_state(sysfs));
+
+		gem_require_mmap_wc(device);
 	}
 
 	igt_describe("Basic error capture");

Do discrete device not support mmap_wc?

Matt

> 
> Known issues
> 
> Here are the changes found in IGTPW_6553 that come from known issues:
> 
> IGT changes
> 
> Issues hit
> 
>   • igt@amdgpu/amd_cs_nop@sync-fork-compute0:
> 
>       □ fi-snb-2600: NOTRUN -> SKIP (fdo#109271) +17 similar issues
>   • igt@gem_exec_fence@basic-busy@bcs0:
> 
>       □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271) +8 similar issues
>   • igt@gem_huc_copy@huc-copy:
> 
>       □ fi-skl-6600u: NOTRUN -> SKIP (fdo#109271 / i915#2190)
> 
>       □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271 / i915#2190)
> 
>   • igt@gem_lmem_swapping@basic:
> 
>       □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271 / i915#4613) +3 similar
>         issues
>   • igt@gem_lmem_swapping@verify-random:
> 
>       □ fi-skl-6600u: NOTRUN -> SKIP (fdo#109271 / i915#4613) +3 similar issues
>   • igt@i915_pm_rps@basic-api:
> 
>       □ bat-dg1-6: PASS -> FAIL (i915#4032)
>   • igt@i915_selftest@live:
> 
>       □ fi-skl-6600u: NOTRUN -> INCOMPLETE (i915#4794)
>   • igt@i915_selftest@live@gt_pm:
> 
>       □ fi-kbl-soraka: NOTRUN -> DMESG-FAIL (i915#1886 / i915#2291)
>   • igt@i915_selftest@live@requests:
> 
>       □ fi-blb-e6850: PASS -> DMESG-FAIL (i915#4528)
>   • igt@kms_chamelium@common-hpd-after-suspend:
> 
>       □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271 / fdo#111827) +8 similar
>         issues
>   • igt@kms_chamelium@vga-edid-read:
> 
>       □ fi-skl-6600u: NOTRUN -> SKIP (fdo#109271 / fdo#111827) +8 similar
>         issues
>   • igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
> 
>       □ fi-skl-6600u: NOTRUN -> SKIP (fdo#109271) +3 similar issues
>   • igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
> 
>       □ fi-skl-6600u: NOTRUN -> SKIP (fdo#109271 / i915#533)
> 
>       □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271 / i915#533)
> 
>   • igt@runner@aborted:
> 
>       □ fi-blb-e6850: NOTRUN -> FAIL (fdo#109271 / i915#2403 / i915#4312)
> 
> Possible fixes
> 
>   • igt@gem_exec_suspend@basic-s3@smem:
> 
>       □ fi-skl-6600u: INCOMPLETE (i915#4547) -> PASS
>   • igt@i915_selftest@live@execlists:
> 
>       □ {bat-jsl-1}: DMESG-FAIL -> PASS
>   • igt@i915_selftest@live@hangcheck:
> 
>       □ fi-snb-2600: INCOMPLETE (i915#3921) -> PASS
> 
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
> 
> Build changes
> 
>   • CI: CI-20190529 -> None
>   • IGT: IGT_6326 -> IGTPW_6553
> 
> CI-20190529: 20190529
> CI_DRM_11080: 8f2355c95e279e57a962843e5d7ba38885b3cfb7 @ git://
> anongit.freedesktop.org/gfx-ci/linux
> IGTPW_6553: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6553/index.html
> IGT_6326: ec75f64fcbcf4aac58fbf1bf629e8f59b19db4ce @ https://
> gitlab.freedesktop.org/drm/igt-gpu-tools.git
> 
> == Testlist changes ==
> 
> +igt@i915_hangman@detector
> +igt@i915_hangman@engine-engine-error
> +igt@i915_hangman@engine-engine-hang
> +igt@i915_hangman@engine-error-state-capture
> +igt@i915_hangman@gt-engine-error
> +igt@i915_hangman@gt-engine-hang
> +igt@i915_hangman@gt-error-state-capture
> -igt@i915_hangman@engine-error
> -igt@i915_hangman@engine-hang
> -igt@i915_hangman@error-state-capture
> 
> SECURITY NOTE: file ~/.netrc must not be accessible by others

  reply	other threads:[~2022-01-13 22:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 19:59 [igt-dev] [PATCH v3 i-g-t 00/15] Fixes for i915_hangman and gem_exec_capture John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 01/15] tests/i915/i915_hangman: Add descriptions John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 02/15] lib/hang: Fix igt_require_hang_ring to work with all engines John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 03/15] tests/i915/i915_hangman: Update capture test to use engine structure John.C.Harrison
2022-01-13 19:58   ` [Intel-gfx] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 04/15] tests/i915/i915_hangman: Explicitly test per engine reset vs full GPU reset John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 05/15] tests/i915/i915_hangman: Add uevent test & fix detector John.C.Harrison
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 06/15] tests/i915/i915_hangman: Use the correct context in hangcheck_unterminated John.C.Harrison
2022-01-13 20:00   ` [igt-dev] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 07/15] lib/store: Refactor common store code into helper function John.C.Harrison
2022-01-13 20:10   ` [Intel-gfx] " Matthew Brost
2022-01-13 20:27     ` John Harrison
2022-01-13 20:23       ` Matthew Brost
2022-01-13 20:40         ` John Harrison
2022-01-13 20:50   ` [igt-dev] [PATCH i-g-t] " John.C.Harrison
2022-01-13 20:53     ` [Intel-gfx] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 08/15] tests/i915/i915_hangman: Add alive-ness test after error capture John.C.Harrison
2022-01-13 20:18   ` [igt-dev] [Intel-gfx] " Matthew Brost
2022-01-13 23:24   ` [igt-dev] [PATCH i-g-t] " John.C.Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 09/15] tests/i915/i915_hangman: Remove reliance on context persistance John.C.Harrison
2022-01-13 20:30   ` Matthew Brost
2022-01-13 20:42     ` [Intel-gfx] " John Harrison
2022-01-13 20:38       ` Matthew Brost
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 10/15] tests/i915/i915_hangman: Run background task on all engines John.C.Harrison
2022-01-13 20:48   ` [igt-dev] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 11/15] tests/i915/i915_hangman: Don't let background contexts cause a ban John.C.Harrison
2022-01-13 21:01   ` Matthew Brost
2022-01-13 21:19     ` John Harrison
2022-01-13 21:26   ` [Intel-gfx] [PATCH i-g-t] " John.C.Harrison
2022-01-13 22:30     ` [igt-dev] " Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 12/15] tests/i915/gem_exec_fence: Configure correct context John.C.Harrison
2022-01-13 21:06   ` [Intel-gfx] " Matthew Brost
2022-01-13 21:23     ` John Harrison
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 13/15] lib/i915: Add helper for non-destructive engine property updates John.C.Harrison
2022-01-13 22:33   ` Matthew Brost
2022-01-13 19:59 ` [Intel-gfx] [PATCH v3 i-g-t 14/15] tests/i915/i915_hangman: Configure engine properties for quicker hangs John.C.Harrison
2022-01-13 22:38   ` Matthew Brost
2022-01-13 19:59 ` [igt-dev] [PATCH v3 i-g-t 15/15] tests/i915/gem_exec_capture: Restore engines John.C.Harrison
2022-01-13 23:04   ` Matthew Brost
2022-01-13 22:23 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixes for i915_hangman and gem_exec_capture (rev6) Patchwork
2022-01-13 22:53   ` Matthew Brost [this message]
2022-01-13 23:15     ` John Harrison
2022-01-13 23:25 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Fixes for i915_hangman and gem_exec_capture (rev7) 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=20220113225354.GA27056@jons-linux-dev-box \
    --to=matthew.brost@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