From: "Randhawa, Jagmeet" <jagmeet.randhawa@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>,
<I915-ci-infra@lists.freedesktop.org>
Subject: Re: ✗ CI.xeFULL: failure for tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs
Date: Tue, 5 Nov 2024 12:33:41 -0800 [thread overview]
Message-ID: <e082a1a9-ae9c-4686-b779-e5f3fb2a84d5@intel.com> (raw)
In-Reply-To: <20241028165547.2wzenuqw5l4srbly@kamilkon-desk.igk.intel.com>
On 10/28/2024 9:55 AM, Kamil Konieczny wrote:
> Hi igt-dev,
> On 2024-10-23 at 04:37:55 -0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs
>> URL : https://patchwork.freedesktop.org/series/140336/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from XEIGT_8082_full -> XEIGTPW_11960_full
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with XEIGTPW_11960_full absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in XEIGTPW_11960_full, 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 (4 -> 4)
>> ------------------------------
>>
>> No changes in participating hosts
>>
>> Possible new issues
>> -------------------
>>
>> Here are the unknown changes that may have been introduced in XEIGTPW_11960_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * igt@kms_flip@dpms-vs-vblank-race-interruptible@a-edp1:
>> - shard-lnl: [PASS][1] -> [FAIL][2] +2 other tests fail
>> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8082/shard-lnl-4/igt@kms_flip@dpms-vs-vblank-race-interruptible@a-edp1.html
>> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11960/shard-lnl-2/igt@kms_flip@dpms-vs-vblank-race-interruptible@a-edp1.html
>>
>> * igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff:
>> - shard-lnl: [PASS][3] -> [DMESG-WARN][4]
>> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8082/shard-lnl-2/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff.html
>> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11960/shard-lnl-4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff.html
>>
>> * igt@xe_vm@bind-array-enobufs:
>> - shard-dg2-set2: [PASS][5] -> [FAIL][6]
>> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8082/shard-dg2-436/igt@xe_vm@bind-array-enobufs.html
>> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11960/shard-dg2-463/igt@xe_vm@bind-array-enobufs.html
> Jagmeet, please look into this, was it caused by your patch?
>
> Rest of failures are unrelated,
>
> Regards,
> Kamil
Hey Kamil, I looked into this, and tested my patch on DG2, this was not
caused by my patch. It is unrelated.
Thanks,
Jagmeet
>> * igt@xe_vm@bind-array-exec_queue-many:
>> - shard-dg2-set2: [PASS][7] -> [DMESG-WARN][8] +1 other test dmesg-warn
>> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8082/shard-dg2-435/igt@xe_vm@bind-array-exec_queue-many.html
>> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11960/shard-dg2-466/igt@xe_vm@bind-array-exec_queue-many.html
>>
>>
>> Known issues
>> ------------
>>
>> Here are the changes found in XEIGTPW_11960_full that come from known issues:
>>
> ...cut...
>
>> [Intel XE#944]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/944
>> [Intel XE#958]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/958
>> [i915#2575]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2575
>> [i915#5274]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5274
>>
>>
>> Build changes
>> -------------
>>
>> * IGT: IGT_8082 -> IGTPW_11960
>>
>> IGTPW_11960: d44f495790106e3e64d4540a30faa09c9fc4d1ca @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>> IGT_8082: c8379ec8b26f3c21bae5473706b23da78bd26ffa @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>> xe-2107-beaeaccd284ba3b69b6dbfdc18bb89441fc99a52: beaeaccd284ba3b69b6dbfdc18bb89441fc99a52
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11960/index.html
next prev parent reply other threads:[~2024-11-05 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 20:11 [PATCH] [i-g-t] tests/intel/xe_vm:Reduce n_execs for bind-array-enobufs Jagmeet Randhawa
2024-10-22 21:05 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-10-28 16:56 ` Kamil Konieczny
2024-10-22 21:46 ` ✓ CI.xeBAT: success " Patchwork
2024-10-23 4:37 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-28 16:55 ` Kamil Konieczny
2024-11-05 20:33 ` Randhawa, Jagmeet [this message]
2024-10-23 14:12 ` [PATCH] [i-g-t] " Cavitt, Jonathan
2024-10-23 20:29 ` Randhawa, Jagmeet
2024-10-23 20:35 ` Cavitt, Jonathan
2024-10-28 16:53 ` Kamil Konieczny
2024-11-05 20:31 ` Randhawa, Jagmeet
-- strict thread matches above, loose matches on Subject: below --
2024-11-05 20:29 [PATCH] [i-g-t, v2] tests/intel/xe_vm: Reduce " Jagmeet Randhawa
2024-11-07 1:53 ` ✗ CI.xeFULL: failure for " Patchwork
2024-11-07 20:08 ` Randhawa, Jagmeet
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=e082a1a9-ae9c-4686-b779-e5f3fb2a84d5@intel.com \
--to=jagmeet.randhawa@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
/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