From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: intel-xe@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: ✗ CI.BAT: failure for drm/xe/pm: Add trace for pm functions (rev3)
Date: Thu, 18 Jul 2024 10:50:34 +0200 [thread overview]
Message-ID: <5e3a7614-45ff-4f39-9c3b-9773e3a7f456@linux.intel.com> (raw)
In-Reply-To: <172129225808.272449.5772173783517418061@2413ebb6fbb6>
[-- Attachment #1: Type: text/plain, Size: 3129 bytes --]
On 7/18/2024 10:44 AM, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* drm/xe/pm: Add trace for pm functions (rev3)
> *URL:* https://patchwork.freedesktop.org/series/136186/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136186v3/index.html
>
>
> CI Bug Log - changes from
> xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f_BAT ->
> xe-pw-136186v3_BAT
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-136186v3_BAT absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-136186v3_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 (7 -> 7)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> xe-pw-136186v3_BAT:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_cursor_legacy@basic-flip-before-cursor-legacy:
> o bat-lnl-1: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f/bat-lnl-1/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136186v3/bat-lnl-1/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html>
>
Unrelated failure. Merged to drm-xe-next
Regards,
Nirmoy
> *
>
>
> Known issues
>
> Here are the changes found in xe-pw-136186v3_BAT that come from known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> * igt@kms_frontbuffer_tracking@basic:
> o bat-adlp-7: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html>
> -> DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136186v3/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html>
> (Intel XE#324
> <https://gitlab.freedesktop.org/drm/xe/kernel/issues/324>)
>
>
> Possible fixes
>
> * igt@xe_exec_balancer@twice-virtual-userptr-rebind:
> o {bat-bmg-1}: DMESG-WARN
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f/bat-bmg-1/igt@xe_exec_balancer@twice-virtual-userptr-rebind.html>
> (Intel XE#877
> <https://gitlab.freedesktop.org/drm/xe/kernel/issues/877>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136186v3/bat-bmg-1/igt@xe_exec_balancer@twice-virtual-userptr-rebind.html>
>
> {name}: This element is suppressed. This means it is ignored when
> computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
>
> Build changes
>
> * Linux: xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f ->
> xe-pw-136186v3
>
> IGT_7929: 7929
> xe-1622-c2610cb0857b1e68f684691f6d3e7fb110f7149f:
> c2610cb0857b1e68f684691f6d3e7fb110f7149f
> xe-pw-136186v3: 136186v3
>
[-- Attachment #2: Type: text/html, Size: 5487 bytes --]
next prev parent reply other threads:[~2024-07-18 8:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 12:59 [PATCH v2] drm/xe/pm: Add trace for pm functions Nirmoy Das
2024-07-17 13:20 ` ✓ CI.Patch_applied: success for drm/xe/pm: Add trace for pm functions (rev2) Patchwork
2024-07-17 13:21 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-17 13:22 ` ✓ CI.KUnit: success " Patchwork
2024-07-17 13:27 ` [PATCH v2] drm/xe/pm: Add trace for pm functions Matthew Brost
2024-07-17 13:34 ` ✓ CI.Build: success for drm/xe/pm: Add trace for pm functions (rev2) Patchwork
2024-07-17 13:36 ` ✓ CI.Hooks: " Patchwork
2024-07-17 13:38 ` ✓ CI.checksparse: " Patchwork
2024-07-17 14:14 ` ✓ CI.BAT: " Patchwork
2024-07-17 17:30 ` ✗ CI.FULL: failure " Patchwork
2024-07-18 8:06 ` ✓ CI.Patch_applied: success for drm/xe/pm: Add trace for pm functions (rev3) Patchwork
2024-07-18 8:06 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-18 8:07 ` ✓ CI.KUnit: success " Patchwork
2024-07-18 8:19 ` ✓ CI.Build: " Patchwork
2024-07-18 8:21 ` ✓ CI.Hooks: " Patchwork
2024-07-18 8:23 ` ✓ CI.checksparse: " Patchwork
2024-07-18 8:44 ` ✗ CI.BAT: failure " Patchwork
2024-07-18 8:50 ` Nirmoy Das [this message]
2024-07-18 11:26 ` ✗ CI.FULL: " 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=5e3a7614-45ff-4f39-9c3b-9773e3a7f456@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox