From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
<igt-dev@lists.freedesktop.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
John Harrison <John.C.Harrison@Intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault
Date: Mon, 2 Jun 2025 11:25:41 -0700 [thread overview]
Message-ID: <74ce12fa-b60b-4103-b92b-6f54a3696c44@intel.com> (raw)
In-Reply-To: <0d4c919f-88a1-497d-84f5-25b8cb854d50@intel.com>
On 5/29/2025 1:29 PM, Michal Wajdeczko wrote:
>
> On 29.05.2025 18:23, Daniele Ceraolo Spurio wrote:
>>
>> On 5/29/2025 6:31 AM, Satyanarayana K V P wrote:
>>> Currently, numerous fault messages have been included in the dmesg
>>> ignore list,
>>> and this list continues to expand. Each time a new fault injection
>>> point is
>>> introduced or a new feature is activated, additional fault messages
>>> appear,
>>> making it cumbersome to manage the dmesg ignore list.
>>>
>>> This new patch automatically ignores all error messages from dmesg,
>>> eliminating
>>> the need to add or maintain a dmesg ignore message list.
>> This would make the test almost meaningless. If the test finds an actual
>> bug (i.e., an error we didn't expect), how would CI detect and report it
> but how can you tell upfront, without actually running a test, which
> error is expected and which is not?
>
>> if all errors are ignored? The only situations we would still fail on is
>> when the kernel just dies.
> and that perfectly fins, sine we should look only for BUG and WARNs, as
> it's quite natural and expected that once we inject an error, the driver
> will likely fail to load or proceed, and/or may report some error
> messages, or even try to silently recover, *but* it shouldn't ever crash
>
> and that should be taken as a test goal, not that we look for specific
> error messages that could be changed, omitted, replaced by the different
> driver release or when running on different platform or function
The patch does not look for WARNs though, it ignores all errors with a
"*" filter, even WARNs. I'm still not fully convinced about ignoring
anything, but I can understand the POV of ignoring just messages with
the "ERROR" tag, as suggested in the other replies. I'd be happy with
that kind of solution.
Daniele
>
> Michal
>
>> Daniele
>>
next prev parent reply other threads:[~2025-06-02 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 13:31 [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault Satyanarayana K V P
2025-05-29 14:22 ` Cavitt, Jonathan
2025-05-29 16:23 ` Daniele Ceraolo Spurio
2025-05-29 20:29 ` Michal Wajdeczko
2025-06-02 18:25 ` Daniele Ceraolo Spurio [this message]
2025-06-02 18:30 ` Cavitt, Jonathan
2025-06-02 20:31 ` Daniele Ceraolo Spurio
2025-06-02 21:09 ` Cavitt, Jonathan
2025-06-02 21:31 ` Lucas De Marchi
2025-05-29 18:40 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2025-05-29 20:14 ` [PATCH i-g-t] " Michal Wajdeczko
2025-05-29 21:48 ` Cavitt, Jonathan
2025-05-30 17:39 ` Kamil Konieczny
2025-06-02 13:00 ` Michal Wajdeczko
2025-06-02 15:17 ` Cavitt, Jonathan
2025-05-30 17:38 ` Kamil Konieczny
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=74ce12fa-b60b-4103-b92b-6f54a3696c44@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=John.C.Harrison@Intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=satyanarayana.k.v.p@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.