From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.BAT: failure for drm/xe/guc: Add GuC based register capture for error capture (rev21)
Date: Wed, 18 Sep 2024 19:51:19 -0400 [thread overview]
Message-ID: <a98a7164-7301-41b8-acbe-504341e8d6f7@intel.com> (raw)
In-Reply-To: <71cc5553-9232-4c4e-970a-8e0dd17fc828@intel.com>
Patch for null pointer fix posted:
https://patchwork.freedesktop.org/series/138847/
Extra test triggered with an for-Ci series, with the above patch
included, the failed BAT test get passed.
Link to for-ci series:
https://patchwork.freedesktop.org/series/138780/
Regards,
Zhanjun Dong
On 2024-09-17 11:52 a.m., Dong, Zhanjun wrote:
> The reason caused test failed is not related to this series.
> It is a pre-existing condition of missing NULL pointer check.
> I will post another patch for the fix.
>
> Regards,
> Zhanjun Dong
>
> On 2024-09-13 2:58 p.m., Patchwork wrote:
>> *Patch Details*
>> *Series:* drm/xe/guc: Add GuC based register capture for error
>> capture (rev21)
>> *URL:* https://patchwork.freedesktop.org/series/128077/
>> <https://patchwork.freedesktop.org/series/128077/>
>> *State:* failure
>> *Details:*
>> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128077v21/index.html
>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128077v21/index.html>
>>
>>
>> CI Bug Log - changes from
>> xe-1948-df3eecb1fa97d6d35569c2fa39f0da78b9f13328_BAT ->
>> xe-pw-128077v21_BAT
>>
>>
>> Summary
>>
>> *FAILURE*
>>
>> Serious unknown changes coming with xe-pw-128077v21_BAT absolutely
>> need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in xe-pw-128077v21_BAT, please notify your bug team
>> (I915-ci-infra@lists.freedesktop.org) to allow them
>> to document this new failure mode, which will reduce false positives
>> in CI.
>>
>>
>> Participating hosts (9 -> 9)
>>
>> No changes in participating hosts
>>
>>
>> Possible new issues
>>
>> Here are the unknown changes that may have been introduced in
>> xe-pw-128077v21_BAT:
>>
>>
>> IGT changes
>>
>>
>> Possible regressions
>>
>> * igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit:
>> o bat-lnl-2: PASS
>>
>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1948-df3eecb1fa97d6d35569c2fa39f0da78b9f13328/bat-lnl-2/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html> -> ABORT <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128077v21/bat-lnl-2/igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit.html> +1 other test abort
>>
>>
>> Known issues
>>
>> Here are the changes found in xe-pw-128077v21_BAT that come from known
>> issues:
>>
>>
>> IGT changes
>>
>>
>> Possible fixes
>>
>> * igt@kms_flip@basic-flip-vs-wf_vblank:
>> o bat-lnl-1: FAIL
>>
>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1948-df3eecb1fa97d6d35569c2fa39f0da78b9f13328/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html> (Intel XE#886 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/886>) -> PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128077v21/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html> +1 other test pass
>>
>>
>> Build changes
>>
>> * IGT: IGT_8016 -> IGT_8017
>> * Linux: xe-1948-df3eecb1fa97d6d35569c2fa39f0da78b9f13328 ->
>> xe-pw-128077v21
>>
>> IGT_8016: 786f0469afc0665a02dd82bf17544868188fbdeb @
>> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>> IGT_8017: 8017
>> xe-1948-df3eecb1fa97d6d35569c2fa39f0da78b9f13328:
>> df3eecb1fa97d6d35569c2fa39f0da78b9f13328
>> xe-pw-128077v21: 128077v21
>>
next prev parent reply other threads:[~2024-09-18 23:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 23:09 [PATCH v20 0/6] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 1/6] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 2/6] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 3/6] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 4/6] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 5/6] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-09-12 23:09 ` [PATCH v20 6/6] drm/xe/guc: Save manual engine capture into capture list Zhanjun Dong
2024-09-12 23:14 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev20) Patchwork
2024-09-12 23:15 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-12 23:16 ` ✓ CI.KUnit: success " Patchwork
2024-09-12 23:28 ` ✓ CI.Build: " Patchwork
2024-09-12 23:30 ` ✓ CI.Hooks: " Patchwork
2024-09-12 23:31 ` ✓ CI.checksparse: " Patchwork
2024-09-12 23:50 ` ✗ CI.BAT: failure " Patchwork
2024-09-13 17:04 ` ✗ CI.FULL: " Patchwork
2024-09-13 18:20 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev21) Patchwork
2024-09-13 18:21 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-13 18:22 ` ✓ CI.KUnit: success " Patchwork
2024-09-13 18:33 ` ✓ CI.Build: " Patchwork
2024-09-13 18:36 ` ✓ CI.Hooks: " Patchwork
2024-09-13 18:37 ` ✓ CI.checksparse: " Patchwork
2024-09-13 18:58 ` ✗ CI.BAT: failure " Patchwork
2024-09-17 15:52 ` Dong, Zhanjun
2024-09-18 23:51 ` Dong, Zhanjun [this message]
2024-09-14 13:57 ` ✗ CI.FULL: " Patchwork
2024-09-17 13:47 ` Dong, Zhanjun
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=a98a7164-7301-41b8-acbe-504341e8d6f7@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@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