From: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Matthew Brost <matthew.brost@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Katragadda, MastanX" <mastanx.katragadda@intel.com>
Subject: Re: [igt-dev] [i-g-t] tests/i915/exec_balancer: Added Skip Guc Submission
Date: Wed, 1 Dec 2021 12:36:58 +0100 [thread overview]
Message-ID: <ccf3f049-a67a-ec5b-377d-c23abecbc94b@intel.com> (raw)
In-Reply-To: <400e33dd-8c5f-10ee-c5e9-631ebcf63253@linux.intel.com>
On 01/12/2021 10:46, Tvrtko Ursulin wrote:
>
> On 30/11/2021 16:48, Matthew Brost wrote:
>>
>> IMO this fix is 100% correct as this is a known, tracked issue. It was
>> agreed upon (arch, i915, GuC team) that we just skip these tests with
>> GuC submission.
This does not look like a fix to me - you just disable test to hide the
result. If this issue is recorded with a bug, is tracked - why cant we
just let this test fail till we get this issue fixed?
>
> I915 team is here on upstream as well.
>
> Record those acks publicly would be my ask. Unless some security by
> obscurity is happening here? Until then from me it is a soft nack to
> keep disabling tests which show genuine weaknesses in GuC mode. Soft
> until we get a public record of exactly what is broken and in what
> circumstances, acked by architects publicly as you say they acked it
> somewhere. Commit message devoid of detail is not good enough.
This should be most probably documented in the bug, right? Here we
should just keep the test as is till the issue is fixed. I don't see how
docummenting an issue would enable us to just disable the test.
Radek
next prev parent reply other threads:[~2021-12-01 11:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 1:57 [igt-dev] [i-g-t] tests/i915/exec_balancer: Added Skip Guc Submission Mastan Katragadda
2021-11-26 2:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-11-26 8:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-29 10:30 ` [igt-dev] [i-g-t] " Tvrtko Ursulin
2021-11-29 10:58 ` Katragadda, MastanX
2021-11-29 11:15 ` Tvrtko Ursulin
2021-11-30 16:48 ` Matthew Brost
2021-12-01 9:46 ` Tvrtko Ursulin
2021-12-01 11:36 ` Radoslaw Szwichtenberg [this message]
2021-12-01 11:46 ` Daniel Vetter
2021-12-01 12:14 ` Tvrtko Ursulin
2021-12-01 23:57 ` Matthew Brost
2021-12-01 23:42 ` Matthew Brost
2021-12-02 9:19 ` Petri Latvala
2021-12-02 9:20 ` Tvrtko Ursulin
2021-12-03 19:36 ` Matthew Brost
-- strict thread matches above, loose matches on Subject: below --
2021-12-09 8:20 Mastan Katragadda
2021-12-10 3:20 ` Matthew Brost
2021-12-10 10:02 ` Tvrtko Ursulin
2021-12-22 9:30 ` Tvrtko Ursulin
2021-12-22 21:02 ` John Harrison
2021-12-23 11:08 ` Tvrtko Ursulin
2021-12-23 11:16 ` Surendrakumar Upadhyay, TejaskumarX
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=ccf3f049-a67a-ec5b-377d-c23abecbc94b@intel.com \
--to=radoslaw.szwichtenberg@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mastanx.katragadda@intel.com \
--cc=matthew.brost@intel.com \
--cc=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.